Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Tuakiri TEST/Dev (operational as of March 4, 2011)
  • Tuakiri Prod/Pilot (to be live by April 15, 2011)
Table of Contents
outlinetrue
indent20px

Federation Details

...

  • Register an Organisation for your institution (if not already registered)
  • Wait for the Organisation to be approved
  • Register your IdP under that Organisation
    • Provide the Contact Details for the IdP admin
    • Select the organisation and provide a name and description for your IdP
    • Enter the base URL for your IdP (https://idp.example.org)
    • Enter the PEM encoded certificate used by your IdP for signing Shibboleth assertions (the default is $IDP_HOME/credentials/idp.pem).
    • Select the attributes the IdP will be able to release to the federation
    • Select supported NameID formats. By default, urn:oasis:names:tc:SAML:2.0:nameid-format:transient is already selected. If supporting SAML1, select also urn:mace:shibboleth:1.0:nameIdentifier.
    • Submit the details and wait for your IdP to be approved.

...

The code snippets in this section have values for Tuakiri TEST/DEV federation. Please update them accordingly as per the table above - which boils down to removing the "test" component from the file names / URLs in all of the cases.

NOTE: Check what your IdP home directory is: the directory is typically called shibboleth-idp - and on Debian and Ubuntu systems, it's commonly /usr/local/shibboleth-idp, while on RedHat and CentOS it's /opt/shibboleth-idp. The snippets below are referring to the IdP home directory as $IDP_HOME

  • Download the metadata signing certificate into $IDP_HOME/credentials:
    No Format
    wget http://directory.test.tuakiri.ac.nz/metadata/tuakiri-test-metadata-cert.pem -O /usr/local/shibboleth-idp/$IDP_HOME/credentials/tuakiri-test-metadata-cert.pem
  • In $IDP_HOME/conf/relying-party.xml
    • Add the following snippet into the ChainingMetadataProvider:
      Code Block
      xml
      xml
              <!-- Tuakiri Test -->
              <MetadataProvider<metadata:MetadataProvider id="Tuakiri-TEST" xsi:type="FileBackedHTTPMetadataProvider" xmlns="urn:mace:shibboleth:2.0:metadata"
                                metadataURL="http://directory.test.tuakiri.ac.nz/metadata/tuakiri-test-metadata-signed.xml"
                                backingFile="/usr/local/shibboleth-idp/metadata/tuakiri-test-metadata.xml">
                <MetadataFilter<metadata:MetadataFilter xsi:type="ChainingFilter" xmlns="urn:mace:shibboleth:2.0:metadata">
                  <MetadataFilter<metadata:MetadataFilter xsi:type="SignatureValidation" xmlns="urn:mace:shibboleth:2.0:metadata"
                                  trustEngineRef="shibboleth.MetadataTrustEngine"
                                  requireSignedMetadata="true" />
                </metadata:MetadataFilter>
              </metadata:MetadataProvider>
      
    • And add the following snippet into the <security:TrustEngine id="shibboleth.MetadataTrustEngine" xsi:type="security:StaticExplicitKeySignature"> element:
      Code Block
      xml
      xml
              <security:Credential id="Tuakiri-Test-FederationCredentials-" xsi:type="security:X509Filesystem">
                  <security:Certificate>/usr/local/shibboleth-idp/credentials/tuakiri-test-metadata-cert.pem</security:Certificate>
              </security:Credential>
      
      Note

      Remember to uncomment the <security:TrustEngine id="shibboleth.MetadataTrustEngine" xsi:type="security:StaticExplicitKeySignature"> element if it is still commented out (it is commented out in the default configuration).

  • Configure attribute release/filtering through the federation instead of explicit configuration:
  • Comment out the explicit policy for https://registry.test.tuakiri.ac.nz/shibboleth in $IDP_HOME/conf/attribute-filter.xml
  • Add : add the following entry into <Service <srv:Service id="shibboleth.AttributeFilterEngine" in $IDP_HOME/conf/service.xml (note that the URL varies for each IdP and can has to be obtanined obtained from the Federation Registry):
    Code Block
    xml
    xml
    
            
    <ConfigurationResource
    <srv:ConfigurationResource xsi:type="resource:FileBackedHttpResource"
                                  url="https://registry.test.tuakiri.ac.nz/federationregistry/attributefilter/generate/
    3
    YOUR-IDP-ID"
                                  file="/
    usr
    opt/
    local/
    shibboleth-idp/conf/tuakiri-test-attribute-filter.xml" />
    
    Note

    Note: if your $IDP_HOME is different from /opt/shibboleth-idp, change the file path in the above snippet accordingly.

Now your IdP should be able to access service provides within the Tuakiri (Test/Dev) federation.