Previous Topic: Use Case 10: SAML 2.0 Single Sign-on with No Name ID at the IdP

Next Topic: Use Case 12: SAML 2.0 SSO Using Attributes from a Web Application

Use Case 11: SAML Artifact SSO Using Security Zones

In use case 11, CompanyA, the producer site, wants to protect Web Agent applications and federated partner resources. The protocols that CompanyA uses for federated single sign-on are the SAML 2.0 artifact profile and SAML 2.0 single logoff.

For the federated resources, a persistent user session is required because the SAML artifact profile stores assertions in the session store at the producer-side Policy Server. Consequently, calls must be made to the session store to retrieve the assertion, impacting performance.

The following figure shows a producer site that combines a federated environment and a web application environment.


Copyright © 2010 CA. All rights reserved. Email CA about this topic