The Incommon Federation wiki has moved.

Please visit the new InCommon Federation Library wiki for updated content. Remember to update your bookmarks.

Click in the link above if you are not automatically redirected in 15 seconds.



You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

This page shows how to migrate a production SP deployment to support SAML V2.0 Web Browser SSO. We assume the SP deployment is currently consuming SAML V1.1 assertions and has the ability to consume SAML V2.0 assertions.

Preconditions:

  • The SP deployment is currently in production
  • The SP deployment is currently consuming SAML V1.1 assertions
  • The SP software supports both SAML V1.1 and SAML V2.0 Web Browser SSO

Procedure:

  1. Add one or more SAML V2.0 endpoints to metadata
  2. Add an encryption key to metadata
  3. Wait for the newly updated metadata to propagate throughout the Federation
  4. Configure the software with the corresponding decryption key
  5. Configure the software for SAML V2.0 Web Browser SSO

Procedural details:

Generally speaking, before making any changes to the software configuration, an SP's metadata is updated and allowed to propagate throughout the Federation. Since Web Browser SSO almost always begins at the SP, exposing endpoints in SP metadata that are not supported in software is usually harmless.

At step 1, one or more SAML V2.0 endpoints are added to metadata. See the comprehensive wiki topic on SP Endpoints for requirements and recommendations.

A SAML V2.0 IdP typically encrypts assertions transmitted through the browser, so the SP is obliged to add an encryption key to metadata at step 2. In the InCommon Federation, this is probably already the case since a key in SP metadata is marked as a multiple use key by default. (See the wiki topic on Key Usage for details.)

You must wait for the new metadata to propagate before continuing with the remaining software configuration steps. We recommend you wait three (3) weeks for the metadata to propagate, since any given Federation metadata file has an explicit 3-week lifetime.

At step 4, configure the software with the private decryption key corresponding to the public encryption key in metadata. If an encryption key was already in metadata when you started this procedure, perhaps the decryption key is likewise already configured in software. Double-check your configuration to be sure.

Finally, at step 5, configure your software to issue SAML V2.0 authentication requests and to consume SAML V2.0 assertion responses. One or more endpoint configurations are required, depending on the SAML V2.0 bindings you wish to support. Consult your software's documentation for details.

#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels