Policy Server Guides › Policy Server Configuration Guide › User Directories › User Attribute Mapping › Apply User Attribute Mapping › Customer Use Case

Customer Use Case

This use case shows how you can use a group membership attribute mapping and a constant attribute mapping to identify customers in Directory A and Directory B.

Given:

1. Directory A stores employees, and because an employee of the company can also be a customer, Directory A identifies customers as those employees that belong to:

   cn=Customers,ou=Groups,o=acme.com
   

2. Directory B only stores customers. Directory B does not have a user attribute that identifies customers, because to store a user in Directory B implies that the user is a customer.

Solution:

1. Create a group membership attribute mapping for Directory A:
   • Name the mapping IsCustomer.
   • Define IsCustomer as:

     cn=Customers,ou=Groups,o=acme.com
     

2. Create a constant attribute mapping for Directory B:
   • Name the mapping IsCustomer.
   • Define IsCustomer as TRUE.

Result:

You can reference IsCustomer when defining policies, expressions, or other objects that must determine if the user is a customer, without concern for the directory-specific schema, because the directories are operationally identical. SiteMinder determines that a user is a customer if they belong to cn=Customers,ou=Groups,o=acme.com when referencing Directory A and that every user is a customer when referencing Directory B.