Add Default Security Domain Mappings
Security domain mappings allow you to override the system’s default behavior of adding all users from an LDAP identity source to the top-level security domain. Using security domain mapping, you can configure the system to add users from an LDAP identity source into a specific security domain.
The following table contains examples of mapping from an external identity source to a lower-level security domain, where the hierarchy of the directory is Com > My Company > Sales > Commercial and Com > My Company > Sales > Retail.
Identity Source User Base DN | Security Domain |
ou=commercial,ou=sales,dc=mycompany,dc=com | CommercialSales |
ou=retail,ou=sales,dc=mycompany,dc=com | RetailSales |
Before you begin
The identity source must be in your administrative scope.
You must have the Security Domain Mappings permission.
Procedure
In the Security Console, click Setup > Identity Sources > Default Security Domain Mapping.
In the Identity Source field, select the identity source where you want to add security domain mappings.
In the Security Domain Mapping section, click Add/Update Mapping.
In the Distinguished Name field, enter the full DN for the object in the identity source that you want to map to a security domain. Specify the DN in standard LDAP Data Interchange Format, for example, ou=commercial,ou=sales.
Enter the top-level organizational unit (OU) after the lower-level OU.
From the Security Domain menu, select the security domain to which users in the DN should be added.
For each security domain you want to map, repeat steps 4 to 6.
Click Save.
After you finish
To verify that the default mapping produces the desired results, test the mapping. For more information, see Test Default Security Domain Mappings.
Related Articles
Manage OIDC Claims and Scopes 85Number of Views Featured Integrations for RSA SecurID Access 161Number of Views Error message "can't connect to ace server" with the RSA Apache Web Agent 8.0 145Number of Views RSA SecurID Software Token 5.0 for Windows Quick Start 51Number of Views ERR_SSL_PROTOCOL_ERROR when accessing RSA Authentication Manager Security and Operations Consoles with Google Chrome 117 a… 1.08KNumber of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x