000038551 - Nesting local and collected roles in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Mar 10, 2020
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000038551
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.0.x, 7.1.x, 7.2.0
IssueOne of the strengths of the RSA Identity Governance and Lifecycle offering is the ability to model groupings of user access using our local role management solution. This provides the capability of combining different types of entitlements (access) that are collected from various end points. These local roles, whether they are defined as business, technical or global roles, allow you to customize the necessary access that is required for different jobs in an organization. These become the building blocks of access by allowing you to combine various local roles that will fully define the access needed for your user population.

A local role is different from a collected role. A collected role, like other collected information, is access obtained from an endpoint which maintains that information externally from our system. Like any collected items, a collected global role is suitable to use as an entitlement in a local role. However, the opposite is not true. A potential problem can occur when a user attempts to add a local role as an entitlement to a collected role. The endpoint that maintains the collected role definition does not know anything about our internal (local) roles – which contain entitlements from a number of other types and sources, including other local roles and local entitlements. This makes provisioning of the information difficult, if not impossible, and extremely confusing.
ResolutionAt this time, there are areas of the RSA Identity Governance & Lifecycle application which inadvertently allow the addition of local roles to collected roles. This is not intentional, and RSA plans to remove that capability in future releases.