| | 91 | |
| | 92 | = Service Provider outside of the SPF = |
| | 93 | 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. |
| | 94 | |
| | 95 | We prefer service providers to follow and release R&S and !CoCo. |
| | 96 | |
| | 97 | Steps to be included: |
| | 98 | |
| | 99 | * The SP operator is responsible for '''registering''' '''and''' '''maintaining''' the SP metadata. |
| | 100 | * Put your !md:EntityDescriptor file in the directory !https://github.com/clarin-eric/SPF-SPs-metadata/tree/master/metadata |
| | 101 | * Create a pull request on its 'master' branch as described in: https://github.com/clarin-eric/SPF-SPs-metadata/blob/master/README.md. |
| | 102 | * 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 check_saml_metadata.sh script (!https://github.com/clarin-eric/SAML-metadata-checker) will run automatically on you pull request and the result will be visible in the pull overview. |
| | 103 | * 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. |
| | 104 | * 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 |
| | 105 | * Either by assigning it to a center (preferred) |
| | 106 | * Or by using the <fill in option to add without assigning to a center> |
| | 107 | |
| | 108 | Non SPF SP / staging metadata will not be pushed to eduGain or any of the national federations. |
