This page shows how to configure an SP deployment for SAML V2.0 Web Browser SSO. This applies to new SPs as well as existing SPs migrating from SAML V1.1 to SAML V2.0. We assume the SP software has the ability to issue SAML V2.0 requests and consume SAML V2.0 assertions.
Generally speaking, before making any changes to the software configuration, an SP's metadata is updated for SAML V2.0 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. On the other hand, issuing SAML V2.0 requests without appropriate SAML V2.0 endpoints in metadata is a recipe for disaster!
...