Changes between Version 44 and Version 45 of ServiceProviderFederation

Timestamp:

10/04/17 14:07:06 (7 years ago)

Author:

André Moreira

Comment:

--

ServiceProviderFederation

@@ -33 +33 @@
  * Create a pull request from your modified fork to the original repository.
  * After the pull request is created Travis CI will automatically run the [https://github.com/clarin-eric/SAML-metadata-checker SAML metadata checker] to check the '''XSD validity''' of the file. 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.
- * When your pull request successfully passes XSD validation, a CLARIN SPF operator will merge it into the original repository. Note: the SPF operators will only consider pull requests which are XSD valid for merging. If you cannot make you file successfully pass the XSD validation or you believe you are hitting a false positive. Please create a [https://github.com/clarin-eric/SPF-SPs-metadata/issues/new github issue] explaining the problem.
- * Every hour a cron job automatically checks out the latest production version and publishes it at http://infra.clarin.eu/aai/clarin-sp-metadata.xml
+ * When your pull request successfully passes XSD validation, a CLARIN SPF operator will merge it into the 'master' branch of 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 [https://github.com/clarin-eric/SPF-SPs-metadata/issues/new github issue] explaining the problem.
+ * Every hour a cron job automatically analyzes the latest 'master' version and generates a QA report visible in [https://docs.google.com/spreadsheets/d/1cwg2kiPL2ubzmtw7Ffe0rbQuJpuOoklFHJ10nR3Bn_M/edit#gid=1150504785 this spreadsheet].[[BR]]Check the spreadsheet for relevant entries respecting your SP and fix any outstanding issues following the [https://www.clarin.eu/content/guidelines-saml-metadata-about-your-sp CLARIN SP SAML metadata guidelines].[[BR]]During this stage your new metadata is already staged 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 http://infra.clarin.eu/aai/prod_clarin_sp_metadata.xml
+
 
 == How to add SAML metadata about the CLARIN IdP to your SP configuration ==