Previous Topic: Create a Custom WS-Federation Authentication Scheme

Next Topic: Configure Disambiguation Locally

Locate User Records for Authentication

When you configure an authentication scheme, you define a way for the authentication scheme to look up a user in the local user store. After the correct user is located, the system generates a session for that user. Locating the user in the user store is the process of disambiguation. How Federation Security Services disambiguates a user depends on the configuration of the authentication scheme.

For successful disambiguation, the authentication scheme first determines a LoginID from the assertion. The LoginID is a SiteMinder-specific term that identifies the user. By default, the LoginID is extracted from the Name ID value in the assertion; however, you can also obtain the LoginID by specifying an Xpath query.

After the authentication scheme determines the LoginID, Federation Security Services checks if a search specification is configured for the authentication scheme. If no search specification is defined for the authentication scheme, the LoginID is passed to the Policy Server. The Policy Server uses the LoginID together with the user store search specification to locate the user. For example, if the LoginID value is Username and the LDAP search specification is set to the uid attribute, the Policy Server searches for the user based on the uid value (Username=uid).

If a search specification is configured for the authentication scheme, the LoginID is not passed to the Policy Server. Instead, the search specification is used to locate a user.

The disambiguation process involves two steps:

  1. Obtain the LoginID by the default behavior or by using an Xpath query.
  2. Locate the user in the user store by the default behavior or with a search specification.

Note: The use of Xpath is optional.


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