Another Mapping already exists for the target account attribute warning in RSA Identity Governance & Lifecycle when setting up Attribute Synchronization
Originally Published: 2019-08-09
Article Number
Applies To
RSA Version/Condition: 7.x
Issue
Another Mapping already exists for the target account attribute "{Name of Attribute}" on "{Application/Directory}"
Cause
In the above example, you are trying to define the Department field in the Active Directory data source to be updated to the value of Cost_Center_Name whenever the Cost_Center_Name user attribute is detected as changed. However, the Department field in the Active Directory data source is already defined to be updated to the value of Department whenever the Department user attribute is detected as changed:
The source user attribute Department is mapped to the target account attribute Department in the Active Directory application. Therefore another user attribute (in this case Cost_Center_Name) cannot be mapped to the target account attribute Department.
Resolution
Related Articles
Setting up on-the-fly SOAP logs in production 47Number of Views How to ensure Agent Hosts for RADIUS clients are not required when setting up RSA RADIUS / RSA Authentication Manager 6.1 46Number of Views Custom user attributes are not available under the table options of the Directories/Applications Account tab in RSA Identi… 22Number of Views Setting New Pin when using RADIUS in a LoadBalancer environment usually fails 142Number of Views Setting Up an Application Trust 16Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Release Notes for RSA Authentication Manager 8.8 Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA Authentication Manager 8.9 Release Notes (January 2026) Disabling weak ciphers using port 1813 in RSA Authentication Manager 8.3 patch 1
Don't see what you're looking for?