WARNING!! This page is outdated and currently being replaced. Please do not rely on any information provided by it!'''

1. SAML metadata about SPF SPs: distribution to identity federations by ERIC

1.1. Accepted SVN revisions (in preproduction and production)

Latest: [7121] and all earlier revisions of clarin-sp-metadata.xml

Newer revisions need manual approval and are not yet in the ​SAML metadata published by CLARIN. (which includes both preproduction and production SPs)

1.2. Service Providers in the production SPF

This means the SP entityID is whitelisted. Only the SPs that are whitelisted, will be filtered and passed on to the ​production SAML metadata. In order to be whitelisted an SP needs to have signed the SPF agreement.

All Service Providers in the production SPF will be registered automatically in DFN-AAI and via eduGAIN in various other federations?.

1.2.1. Accepted

See the ​centre registry SPF page, all the SPs with a checked "Prod?" column.

1.2.2. Waiting list

The following SPs are not yet fully functional. Therefore they have not yet been added to the production SPF:

• [7111]+ (HAKA only) reason: pending on HAKA's decision on how to propagate CLARIN SPs metadata to them
• LAP, [7049], reason: not yet working with CLARIN IdP
• CLARIN-LT, [7101], Only missing eduID.cz (to be submmited)

1.3. Actual distribution to national federations

Submission round closing date	Included SVN revision(s)	BE?	CZ?	FI?	NL?
2017-06-15	[7122], [7123], [7127]	submitted: 2017-09-11 updated: 2017-09-12	submitted: [7123] - 2017-09-11; [7122][7127] - not yet updated: not yet	submitted: not yet updated: not yet	submitted: [7127] - 2017-07-19; [7123] - 2017-09-11; [7122] - not yet updated: [7127] - 2017-07-21; [7123] - 2017-09-11; [7122] - not yet
2017-04-12	[7114], [7118], [7119], [7121]	submitted: 2017-04-12 updated: 2017-04-13: [7118], [7121]	submitted: 2017-04-12 updated: 2017-04-13	submitted: not yet updated: not yet	submitted: 2017-04-12 updated: 2017-04-12
2017-02-22	[7113]	submitted: 2017-02-28 updated: 2017-04-13	submitted: 2017-02-28 updated: 2017-03-01	submitted: not yet updated: not yet	submitted: 2017-02-28 updated: 2017-02-28
2017-02-01	[7111]	submitted: 2017-02-01 updated: 2017-02-14	submitted: 2017-02-01 updated: 2017-02-01	submitted: not yet updated: not yet	submitted: 2017-02-01 updated: 2017-02-01
2017-01-26	[7108], [7109]	submitted: 2017-01-25 updated: 2017-01-25	submitted: 2017-01-26 updated: 2017-01-26	submitted: 2017-01-26 updated: 2017-01-27	submitted: 2017-01-26 updated: 2017-01-26
2016-12-15	[7095], [7102], [7104]	submitted: 2017-01-05 updated: not yet	submitted: 2016-12-20 updated: 2016-12-21	submitted: not yet updated: not yet	submitted: 2016-12-20 updated: 2016-12-20
2016-08-25	[7046]	submitted: 2016-08-29 updated: 2016-08-31	submitted: 2016-09-12 reminder: 2016-10-19	submitted: 2016-09-12 updated: 2016-09-27	submitted: 2016-09-12 updated: 2016-09-12

Please note: for the other countries we use the eduGAIN metadata distribution?. Therefore they are not listed in the distribution matrix.

For an explanation about why this dual distribution mechanism is in use, please see the ​opt-in page.

2. Procedure for changing/adding and distributing new SAML metadata about SPF SPs

Adding a new SP or changing SAML metadata about an existing one and distributing it is a complicated procedure.

1. Check new e-mails to spf@clarin.eu with subjects of the form Commit (7047) by martynas.savickis@bpti.lt to SAML metadata about SPF SPs.
2. Check ​the single SAML metadata batch in the SVN at all revisions recorded in the previous e-mails. Criteria are correctness and security (partly covered by the ​guidelines).
3. Make an edit similar to ​this one on ems04.mpi.nl:/srv/Python/venvs/2014-11-20_SPF/etc/pyff_config/control.sh. See the host page ems04.mpi.nl for info on ems04.mpi.nl. Also be sure to push the same change as a commit to the ​relevant Git repo.
4. Cron job 11 running under the superuser on ems04.mpi.nl will update the SAML metadata batch at ​https://infra.clarin.eu/aai/md_about_spf_sps.xml. The CLARIN IdP will use this preproduction batch.
5. Check ​this Google Sheets spreadsheet, sheet md_about_spf_sps. This sheet details the results of validation of this SAML metadata batch. Follow up with the committers (i.e., SP operators) on whether their submissions meet the ​guidelines based on e.g. this sheet.
6. Once any validation issues have been resolved, organize login tests for every new SP using the CLARIN IdP.
7. Next, mark every new SP entity as production SP. You can do this by adding the SP's entity ID to the list in ems04.mpi.nl:/srv/Python/venvs/2014-11-20_SPF/etc/pyff_config/job_b.fd. Again, also make that change over at the ​relevant Git repo.
8. Cron job 11 running under the superuser on ems04.mpi.nl will update the SAML metadata batches under ​https://infra.clarin.eu/aai/ (this time, including prod_md_about_spf_sps.xml).
9. To help everyone track new SPs and their registration statuses across identity federations, add the SPs to the ​Centre Registry.
10. Cronjob 17 running under user www-data on ems04.mpi.nl will use the information in the Centre Registry to analyze the SAML metadata batches under ​https://infra.clarin.eu/aai/ into useful pieces under ​https://infra.clarin.eu/aai/sps_at_identity_federations/.
11. DFN-AAI (DE?) will pick up the mutations to ​SAML metadata batch. This will ensure that it is distributed throughout eduGAIN, and reviewed additionally by DFN-AAI.
12. Once DFN-AAI has picked up the new SP (and thus the SP is in eduGAIN), which you can determine via the ​Centre Registry, add the SP to further identity federations. Click on the country code columns in the above table for details on the identity federation-specific procedure.
13. Finally, check whether any new SP has been registered for multiple identity federations using ​this eduGAIN webapp (i.e., a clash). In case a clash is found, request the SP operator to remove the registration with any federation other than the CLARIN SPF.

3. Issues with production SPs

Please avoid expiring SAML signing certificates by doing a ​certificate roll-over on time.

• SAML-signing certificate of ​http://www.clarin-pl.eu/shibboleth expires on Sun, 08 Jan 2017 11:48:16 +0100
• Remedy: create new SAML metadata, sign with a valid certificate (could be self-signed)