How attribute information is collected
Information can be collected by:
The auto discovery process, which loads account attribute information – from target systems that support attribute listing – into mapped profile and request attributes.
A plugin that automatically collects and/or generates or looks up information, such as an employee ID, from a database.
To learn how to configure and write such a program, see Validating and generating attribute values .
Users who update profile information using the web interface.
To learn how end users update attributes using the self-service form, see Update attributes.
Click below to view a demonstration.
Mapping profile and request attributes
You can map profile and request attributes to account attributes to load users’ information from a target system. You can also configure attributes so that users’ accounts are updated when their profile information is updated.
The type and number of values of the profile and request attribute must be compatible with the account attribute. For example, you cannot map a required account attribute to an optional profile and request attribute, or a single-valued account attribute to a multi-valued profile and request attribute.
See Account attributes for more information about mapping attributes.
Grouping attributes
Attributes must be included in an attribute group in order to be used. You can organize attributes into groups to:
Assign read and write privileges to users in different stages of authorization workflow.
Assign read and write privileges to creators of managed system policies, when Bravura Privilege features are used.
Determine whether attributes are displayed for specific operations, such as view profile.
Determine how attributes are displayed to users on the request form.
See Attribute groups for details.
Enforcing validation
Normally, if a value is required, Bravura Security Fabric stops a request from proceeding if the user has not entered a correctly formatted value. You can turn off validation for an attribute or attribute group if an incorrectly entered value should not block a request. This can be useful, for example, if a user needs to create or update their profile but does not have complete information.
If used, the attribute validation plugin overrides these settings.
See also