Note: this page is in the process of being updated (Oct 2017)

A good starting point for information about the Service Provider Federation is the public page

This wiki page contains the nitty-gritty technical details.


See InfrastructureOverview#CLARINIdentityProvider

Central Discovery Service

See InfrastructureOverview#DiscoveryService

Service Provider Federation

  • Recommendations on certificates: use self-signed ones for the SAML metadata and well-accepted ones for your webserver.

Changing the SAML metadata about SPF SPs

[New SP File Name] = [SP entityID].replace("http(s)?://", "").replace("/", "%2F")

  • Create a pull request from your modified fork to the master branch of the original repository.
  • After the pull request is created, Travis CI will automatically run the SAML metadata checker to check the XSD validity of the file. You can monitor the check progress and result in the pull request page as in this example. Wait for the check to finish and make sure you get a green check-mark in the end. If instead you see a red X mark, please fix your commit based on TravisCI output information and update the pull request. To see the test output, click on the result icon (V or X) which takes you to the TravisCI interface.
  • When your pull request successfully passes XSD validation, a CLARIN SPF operator will merge it into the master branch of the original repository for QA assessment. Note: the SPF operators will only consider for merging pull requests which are XSD valid. If you cannot make you file successfully pass the XSD validation or you believe you are hitting a false positive. Please create a github issue explaining the problem.
  • After your pull request is merged, Travis CI will automatically analyze the latest master version and generate a QA report visible in this table.
    Wait for the new QA report to be generated: Travis CI will post a comment on your merged pull request indicating that the new QA report is available and for which SPs the QA report changed.
    Check the table for relevant entries respecting your SP and fix any outstanding issues following the CLARIN SP SAML metadata guidelines. Then, create a new pull request containing any necessary fixes.
    During this stage your new metadata is already scheduled to be merged into the production branch and consequent propagation to the various identity federations. However, before this happens and depending on the QA results for your SP, you might be contacted by an SPF operator to fix or improve your metadata before propagation.
  • Finally your metadata will be merged into the production branch and picked up by an hourly cron job which automatically checks out the latest version and publishes it at

How to add SAML metadata about the CLARIN IdP to your SP configuration

Information per Identity Federation

(original source no longer available))

Haka (Finland)

cn, sn, displayName, eduPersonPrincipalName, schacHomeOrganization, schacHomeOrganizationType

The major unique identifier: Currently, ePPN is the predominant unique ID.

The federation operator has published instructions on use of ePTID but hasn't strongly insisted its use.



sn, email, ePPN, ePSA, ePEntitlement, ePTID

What is the predominant unique identifier for end users?

  • eduPersonPrincipalName (ePPN)
  • eduPersonTargetedID(ePTID)/SAML2 PersistentID

Is there a policy for what should be used as the unique ID? No.


Mandatory attributes: No mandatory attributes

The major unique identifier: eduPersonPrincipalName (ePPN) - there is no formal policy for what should be used as the unique ID

UK federation

See section 7 of for the recommended attributes in the UK.

Requesting changes to the IdP blacklist

Attributes in the SPF

The minimal set of required attributes:

The ideal set of attributes:

Attribute release

Attributes requested by SPF services

These should be listed in the SAML metadata about the SP - see recommendation 8 (attributeconsumingservice) of

Service Provider outside of the SPF

Sometimes a service provider and CLARIN reach an agreement about enabling login with CLARIN user accounts for that specific SP. For these cases the service provider metadata can be added to the staging feed.

We prefer service providers to follow and release R&S and CoCo.

Steps to be included:

  • The SP operator is responsible for registering and maintaining the SP metadata.
    • Put your md:EntityDescriptor file in the directory 
    • Create a pull request on its 'master' branch as described in:
    • Make sure the clarin-sp-metadata.xml file is still valid after your very last edit. To help you with this, after creating the pull request, the script ( will run automatically on you pull request and the result will be visible in the pull overview. 
    • Only pull requests that pass this check will be considered. After this, the central office will review your SAML metadata and if no outstanding issues are found, merge add it to the CLARIN SPF pre-production metadata source file.
  • Once the pull request is accepted and passed quality checks, the SPF operator can include the SP in the staging feed by adding it to the centre registry
    • Either by assigning it to a center (preferred)
    • Or by using the <fill in option to add without assigning to a center>

Non SPF SP / staging metadata will not be pushed to eduGain or any of the national federations.

Last modified 3 years ago Last modified on 06/18/21 11:08:40