Overview

The usual method for defining proposal lists for role parameters of type String is to define the proposal list and the attribute that holds the proposal so that the proposal values are fixed.

Sometimes, however, it makes sense to have proposal lists for role parameters that are user specific. For example, every user has a special set of computers which should act as role parameters. In the solution described in this use case, these values can be provided in a special multi-value user attribute or in a business object referenced by the user. With this method, each user has its own proposals.

For detailed information on users, business objects, role parameters and proposal lists and object descriptions, see the DirX Identity Customization Guide, the DirX Identity Provisioning Administration Guide and the DirX Identity Manager context-sensitive help.