What is the impact of a domain migration in RSA Identity Governance and Lifecycle

Originally Published: 2016-10-17

Last Modified: 2023-10-06

Article Number

000065232

Applies To

RSA Product Set: RSA Identity Governance and Lifecycle
RSA Version/Condition: 6.9 +

Issue

This article discusses the impact of Domain Name changes on the RSA Identity Governance and Lifecycle product.

Customer Scenario

To prepare for a domain consolidation project, users have been imported from production domain into a sub-level OU in a test domain.
Now that migration has actually started, the users need to be imported into a different OU at the primary level to match the production OU.
Do the rules and roles need to be updated to change from one OU to another?

Tasks

For further information on domain name, please review the following documents;

For RSA Identity Management and Governance 6.8 and 6.9, review the RSA Identity Management & Governance 6.8.1 Collectors Guide, Appendix A: Data Collection Parameters.
For RSA Identity Management and Governance 6.9 Access Fulfillment Express, review the RSA Identity Management & Governance 6.9.1 AFX Connector Configuration Guide.
For Via Lifecycle and Governance 7.0.0 and Identity Governance and Lifecycle 7.0.1, review the RSA Connector & Collector Application Guides.

Resolution

Rules and roles do not need to be changed, providing the recommended Entitlement Name format has been followed. The recommended Entitlement Name format is the resource:action pair name, for example:

Entitlement Name = Account : Edit All

For the RSA Identity Governance and Lifecycle product, Domain Name changes should only impact Collector and Connector definitions, and Account Entitlements (typically collected from an LDAP source, like Microsoft's Active Directory). For all other objects, once the data is collected, the Domain Name is no longer used. Domain Names are typically used to identify Internet resources, such as computers, networks, and services, but not users, accounts, application names or Entitlements.

Further to the Customer Scenario above, an organizational unit (OU) is different from a Domain Name. An OU provides a way of classifying objects located in directories, or names in a digital certificate hierarchy. OUs are typically used either to differentiate between objects with the same name, or to organize object creation and management. However, an example where a change in the OU may be an issue is with an Account Entitlement.

Entitlement Name = CN=ACME_Users,OU=OU_Applications,OU=OU_AccessGroups,DC=acme,DC=com

In this case, if the users need to be imported into a different OU, then RSA Identity Governance and Lifecycle can only treat them as different to the OU data it already has stored. Therefore, the different OU data would need to be Collected as part of an Account Data Collection, rather than being modified within the RSA Identity Governance and Lifecycle product.

Don't see what you're looking for?

Customer Scenario

Related Articles

Trending Articles