Links may not function; however, this content may be relevant to outdated versions of the product.
Storage of operator security attributes
For the system of record, security attributes can be stored and maintained internally or externally to Pega Platform. You can access the operator security attributes that are used in policy conditions in several ways.
- If attributes are stored internally, then it is likely that they are stored in the operator record or a new data class, which makes them already accessible to policy conditions.
- If the attributes are stored externally, then these attributes need to be retrieved
during login and stored somewhere in Pega Platform where policy
conditions can access them.
Custom authentication allows the policy conditions to access the attributes. Depending on their requirements, users can choose to use the custom authentication activity or the Mapping tab on the Authentication Service form, or they can use both options. For example, mapping can be used to copy data stored in an LDAP directory directly in properties in the Data-Admin-Operator-ID class. If mapping is more complex, then an activity can be used to retrieve the attributes from the external location and copy them to a location within the application created in Pega Platform (for example, a requestor-scoped data page).
Previous topic Security attributes markings Next topic One Of and All Of conditions