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

Version 1 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

Procedure:

  1. Add one or more SAML 2.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 to issue SAML V2.0 authentication requests

Procedural details:

TBD

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