Skip to main content

Mapping account attributes to profile and request attributes

Profile and request attributes allow any number of account attributes to be mapped to a single value in users’ profile data. Several attributes are mapped by default; for example, the Active Directory mail and Lotus Domino Server InternetAddress account attributes are mapped to the EMAIL profile and request attribute. Attributes that are mapped to profile and request attributes are listed by default when the target system’s List attributes setting is enabled.

To map an account attribute to a profile and request attribute, the attributes’ requirements (number of values, attribute type, encoding) must be compatible.

If a profile attribute is set to not display in reports, the mapped account attribute will also not display in reports.

Click below to view a demonstration:

To map an account attribute to a profile and request attribute:

  1. Select an override level .

  2. Select an account attribute.

  3. Choose the profile and request attribute to map to. You can either:

    • Search for the profile and request attribute.

    • Type the profile and request attribute ID in the Map account attribute to profile/request attribute field

    • Create a new profile and request attribute:

      1. Click the search icon 3332.png .

      2. Click plus icon Add new ...

      3. Configure the options defined in Getting started .

      4. Close the profile and request attribute attribute information pop-up window.

    The Populate mapped profile attribute with values from target system will automatically be selected when the Map account attribute to profile and request attribute field is filled in and when the Load attribute values from target system has been checked. You can disable the mapping of attributes by deselecting this box.

  4. Click Update.

Mapping target system boolean attribute values

Profile and resource attributes in Bravura Security Fabric represent boolean values internally using T and F for true and false, respectively. However, target systems may use values other than T and F to represent boolean attribute values. Use the configuration settings Target system attribute value that represents [True] and Target system attribute value that represents [False] to ensure that target system boolean attribute values are converted correctly to mapped profile or resource attributes. For example, if a target system attribute uses 1 for true and 0 for false, then set Target system attribute value that represents [True] to 1 and Target system attribute value that represents [False] to 0.

In this section: