Changes between Version 11 and Version 12 of ServiceProviderFederation/Archive/SP configuration guide

Timestamp:

08/18/14 12:06:15 (10 years ago)

Author:

Sander Maijers

Comment:

--

ServiceProviderFederation/Archive/SP configuration guide

@@ -6 +6 @@
 This document does not have as much priority for regular revision as the following documents. Please consult them and do not fully rely on the details in this document. 
 * Up-to-date information about the CLARIN Service Provider Federation (SPF): [https://www.clarin.eu/spf]
-* Up-to-date information about the CLARIN-IDP [https://www.clarin.eu/content/clarin-identity-provider]
+* Up-to-date information about the CLARIN IdP [https://www.clarin.eu/content/clarin-identity-provider]
 * Generate the metadata and additional information: [https://wiki.shibboleth.net/confluence/display/SHIB2/MetadataForSP]
 * !ApplicationDefaults tag and attributes: [https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPApplication]
@@ -16 +16 @@
 
 == Installation ==
-
-Install Shibboleth daemon on your server in desirable or standard way. 
+Install Shibboleth daemon on your server in desirable (possibly through a standard OS package) way. 
 
 == Configuration ==
@@ -34 +33 @@
 
 ==== shibboleth2.xml ====
-Edit `shibboleth2.xml` (usually located in the directory `/etc/shibboleth`):
-* Add an `<ApplicationDefaults>` entry containing your `entityID`. The `entityID` is a randomly chosen string in URL-format identifying your SP (and letting other people make some assumptions about who runs the SP):
+Edit `shibboleth2.xml` (on Unix usually located in the directory `/etc/shibboleth`):
+* Add an `<ApplicationDefaults>` entry containing your `entityID`. The `entityID` is an arbitrary string in URI format identifying your SP (and letting others make some assumptions about who runs the SP):
 {{{#!xml
-<ApplicationDefaults entityID="https://sp.phonetik.uni-muenchen.de" 
+<ApplicationDefaults entityID="https://your-further-entity-id" 
                      REMOTE_USER="persistent-id">
 }}}
 
-* Add an `<SSO>` entry to the Session section with the entityID of the CLARIN-IDP and the link to the discovery service:
+* Add an `<SSO>` entry to the Session section with the `entityID` of the CLARIN IdP and the link to the Discovery service:
 {{{#!xml
 <SSO entityID="https://idp.clarin.eu" discoveryProtocol="SAMLDS" 
@@ -49 +48 @@
 }}}
 
-* Edit the errors section to let the user know who he or she may contact on error:
+* Edit the Errors element to let the user know who he or she may contact in case of an error:
 {{{#!xml
 <Errors supportContact="your-username@your-institution.com"
@@ -61 +60 @@
               backingFilePath="prod_md_about_clarin_erics_idp.xml" reloadInterval="7200">
 }}}
-
 
 
@@ -81 +79 @@
 ==== metadata.xml (cp. [ssec:meta]) ====
 
-1. Checkout the clarin-sp-metadata.xml from https://svn.clarin.eu/aai/ ;
-1. Get the metadata from your own server (https://yourserver/Shibboleth.sso/Metadata) (cp. [sssec:metaorig]) Correct the metadata (changing namespaces, etc. accordingly) (cp. [sssec:metacorr])
+1. Checkout the clarin-sp-metadata.xml from [https://svn.clarin.eu/aai/].
+1. Get the metadata from your own server (https://yourserver/Shibboleth.sso/Metadata) (cp. [sssec:metaorig]) Correct the metadata (changing namespaces, etc. accordingly) (cp. [sssec:metacorr]).
 1. Open the clarin-sp-metadata.xml and go to the section for the metadata of your Shibboleth server or create one.
-1. Add your corrected metadata to the section
+1. Add your corrected metadata to the section.
 1. Execute check_saml_metadata.sh from subdirectory check-saml-metadata to validate the XML file. 
-1. Commit the changes back to the svn server
-1. Wait for the next update process (which should happen every hour, so it could take up to an hour until you can log in)
+1. Commit the changes back to [https://svn.clarin.eu/aai/].
+1. Wait for the next update (which should happen every hour, so it could take up to an hour until you can log in)
 
 = Appendix =