Core Concepts & Architecture
Architectural blueprints, Active Directory service accounts, attribute synchronization rules, and data processor patterns for RSA Governance & Lifecycle.
Provisioning Command Response Handling
A Provisioning Command activity in an RSA Identity Governance & Lifecycle (G&L) workflow sends an account change to a target connector. By default, the activity's own success/failure transition only confirms that the node executed. It does not confirm whether the target system actually applied the change. To get the real outcome, enable Wait for Result and read the status job properties it populates.
Active Directory Service Account for RSA G&L
RSA Governance and Lifecycle (G&L) connects to Active Directory using a dedicated service account. G&L authenticates with a username and password (LDAP simple bind), so the account must be a standard AD user account, not a group-managed service account (gMSA).
Attribute Synchronization
In this guide, we will explore the process of attribute synchronization using RSA Governance & Lifecycle (RSA G&L), focusing on how it ensures consistency between user identity data and account data across various downstream systems. By automating the synchronization of attributes such as roles, email addresses, and group memberships, RSA G&L simplifies identity management, reduces errors, and ensures that all connected systems maintain accurate and up-to-date information.
Adding a Custom JDBC Driver
RSA Governance and Lifecycle (G&L) 8.0 and later uses a single generic database connector that replaces the individual per-database connectors from earlier versions. The generic connector supports the following databases:
Manipulating Accounts
In this blog post, I will guide you through the effective utilization of data processors during account collections to address common use cases. If you are not familiar with data processors, I recommend reading the Data Processors Basics before proceeding, as it will provide a foundational understanding of the concepts discussed in this blog.
Manipulating Identities
In this blog post, I will guide you through the effective utilization of pre and post processors during identity collections to address common use cases. If you are not familiar with data processors, I recommend reading the Data Processors Basics before proceeding, as it will provide a foundational understanding for the concepts discussed in this blog.
Data Processor Basics
Data processors have been integral in RSA Governance and Lifecycle (G&L) systems, playing a crucial role in manipulating data throughout different stages of collections, unification or Separation of Duties (SoD) processing. Traditionally, the integration of custom logic into these data processors required direct system access to the AVDB database and the use of tools such as SQL Developer. However, with the evolution of G&L products, there has been a paradigm shift in the approach to implementing custom logic within data processors.
REST Collector Authentication
In recent blog posts, we've explored numerous integrations between RSA G&L and various SaaS applications, primarily relying on the Generic REST collectors. Despite their flexibility, navigating through the intricate components of these collectors can be overwhelming. This article aims to simplify the process by focusing on the authentication aspect, providing an overview of the supported authentication methods and offering common examples to clarify the integration process.