RSA Authentication Manager Bulk Administration Is Reporting A Communication Error
Originally Published: 2017-05-04
Article Number
Applies To
RSA Product/Service Type : RSA Authentication Manager
RSA Version/Condition: 8.1 Service Pack 1
Platform : SUSE Enterprise Linux
O/S Version : 11 Service Pack 3
Product Description : SecurID Appliance
Issue
RSA Authentication Manager Bulk Administration is used at the command line using the following format from the /opt/rsa/am/utils folder: ./rsautil AMBulkAdmin -i <datafile> -a <superadmin> -P <password>
Cause
Resolution
- Logon with the rsaadmin account when using RSA Authentication Manager Bulk Administration.
- Check the permissions of /opt/rsa/am/utils/lib/AMBulkAdmin.jar. It is expected that AMBulkAdmin.jar has -rw-r--r-- file permissions, is owned by rsaadmin and the group is rsaadmin e.g. -rw-r--r-- 1 rsaadmin rsaadmin 258371 May 13 2013 AMBulkAdmin.jar
- Test the credentials used at the command line with RSA Authentication Manager Bulk Administration with the Security Console and confirm the password is working and that the administrative account has a SuperAdminRole.
- After confirming the credentials are correct and has appropriate administrative rights then consider changing the password, especially if a special character is used in the password e.g. $
Related Articles
How to capture web sessions using Fiddler for troubleshooting purposes 324Number of Views Password Capture Tool is not creating password synchronization requests in RSA Governance & Lifecycle 79Number of Views Trusted Realms 8Number of Views View Trusted Realm Settings 3Number of Views Unassign an Agent from a RADIUS Profile 3Number of Views
Trending Articles
RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Unable to login to RSA Authentication Manager Security Console as super admin Error Unable to resolve user by login ID and/or alias, or authenticator not assigned to user when attempting to authentica…
Don't see what you're looking for?