Authentication Manager 8.x
Active Directory users
Internal Database users
In the case of acquisitions and mergers, sometimes companies want to unify the username format. If one company uses firstname.lastname, and the other uses an abbreviated lastname with first initial, it makes sense to unify these into one standard format. This means we have to change some of the usernames to match the format of the others.
Internal Database: Assuming we have an Enterprise license, we can run an AMBA script to change the username format.
Active Directory: If we have an external identity source, AM only has a read-only connection. We need a PowerShell script to convert the username format.
Recommendations:
- As always, MAKE A BACKUP before attempting.
- Prudence dictates running a script on one or two users to validate results, before attempting to run in bulk.
Internal Database
- Create an AMBA script with the following columns (Excel is very useful for this:)
Action,DefLogin,MiscVariable
- Populate the file with the corresponding information:
Action,DefLogin,MiscVariable UUD,planey.mcplaneface,mcplap
- Save you file (in this example we will call it amba-UUD.csv).
- Copy this file to your Authentication Manager Primary using WinSCP or similar. You can put it in /opt/rsa/am/utils, or /home/rsaadmin. Just make a note of the path and filename.
- Invoke AMBA using the following command. For security reasons, you should always put your credentials in an .ini file. See https://community.rsa.com/s/article/RSA-Authentication-Manager-Bulk-Admin-AMBA-Crash-Course for more details on how to do this. An example.ini file is attached to this article.
cd /opt/rsa/am/utils
./rsautil AMBulkAdmin --ini example.ini
6. Before and after of one user after running the script:
Before:
After:
Active Directory
For AD users, we will need to build a similar CSV file, and run the attached PowerShell script from the Domain Controller.
- First, create an input file called ADusers.csv. There should be three columns:SamAccountName,NewSamAccountName,NewUPN
- Add your data following the header format:SamAccountName,NewSamAccountName,NewUPN
mcboab,boaty.mcboatface,boaty.mcboatface@securidcs.net - Copy this file and the attached PowerShell script to the same directory on your Domain Controller.
- Run the script:rename_AD_users.ps1
- Before and after screenshots from the Security Console:
Before:
After:
As always, MAKE A BACKUP before attempting the steps above.
Prudence dictates running a script on one or two users to validate results, before attempting to run in bulk.
Related Articles
How to identify your RSA Authentication Manager version, service pack, patch and hotfix level 33Number of Views Certificates and Keys for Service Providers and Identity Providers for the SSO Agent 19Number of Views RSA Authentication Manager 8.2 fails to be applied to an RSA Authentication Manager 8.1 Service Pack 1 replica instance 271Number of Views Error 2004: Unable to communicate with server Access Denied when running RSA Authentication Manager Bulk Admin (AMBA) script 234Number of Views Comparing certificates used in RSA Authentication Manager, Cloud Authentication Service, and hybrid deployments 16Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA Authentication Manager 8.9 Setup and Configuration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device