LDAPv3 User Verification for Cloud Access Service
LDAPv3 User Verification for Cloud Access Service
The identity router verifies the user’s identity source account by checking with the directory server. If the account is enabled, the identity router sends the Authenticate OTP to the Cloud Access Service (CAS) for verification. If your deployment uses an LDAPv3 identity source, RSA checks the following user attributes to determine the user's disabled status.
| Attribute | Setting |
|---|---|
| ds-pwp-account-disabled | true for disabled accounts. |
| nsaccountlock | true for disabled accounts. |
| shadowExpire | 0 for disabled accounts. |
If your LDAPv3 server does not use these attributes to indicate disabled status, RSA treats all users in the identity source as enabled.
Related Articles
Local Entitlement stays in pending verification state in RSA Governance & Lifecycle Number of Views Live Verification Policy Number of Views Change requests provisioned by AFX remain in "pending action" or "pending verification" in RSA Governance & Lifecycle Number of Views RSA Self Service module will not allow special characters in the username. Number of Views Live Verification for Users Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) How to install the jTDS JDBC driver on WildFly for use with Data Collections in RSA Identity Governance & Lifecycle RSA Authentication Manager 8.8 Setup and Configuration Guide Artifacts to gather in RSA Identity Governance & Lifecycle
Don't see what you're looking for?
