Configuration Guides › Federation Security Services Guide › Federation Security Services Overview › Federation Use Cases › Use Case 10: SAML 2.0 Single Sign-on with No Name ID at the IdP

Previous Topic: Use Case 9: SAML 2.0 User Authorization Based on a User Attribute

Next Topic: Use Case 11: SAML Artifact SSO Using Security Zones
Use Case 10: SAML 2.0 Single Sign-on with No Name ID at the IdP

In Use Case 10, discounts.com purchases widgets from smwidgets.com.

A buyer for discounts.com clicks on a link to access the latest price list on widgets at smwidgets.com. The buyer is taken to the smwidgets.com website and presented with the price list without having to log on to discounts.com website.

The following illustration shows this use case.

SSO witn No User Record at IdP

Discounts.com requests access to a price list at smwidgets.com. No federated user identity is stored at discounts.com for its buyers or at smwidgets.com. When a request from discounts.com is sent to smwidgets.com, this entity creates an identity for the buyer that it sends back in a secure manner to discounts.com. Discounts.com uses this identity to authenticate the user and allow the buyer access to the requested resource.