Previous Topic: First Name Use Case

Next Topic: Sort Name Use Case

Last Name Use Case

This use case shows how you can use two alias attribute mappings to represent the last name user attribute in Directory A and Directory B.

Given:

User Directory A identifies the last name of users with surname. Directory B identifies the last name of users with u_last_name. This results in two different representations and views of the same user information.

Solution:

  1. Create an alias attribute mapping for Directory A.
  2. Create an alias attribute mapping for Directory B.

Result:

You can reference LastName when defining policies, expressions, or other objects that require the last name of users, without concern for the directory-specific schema, because the directories are operationally identical. SiteMinder determines that the last name of users is identified by surname when referencing users in Directory A and is identified by u_last_name when referencing users in Directory B.


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