Import Bulk Requests for User Groups and Tokens
You must run the import-bulk-request utility on the appliance. The input file must also be on the appliance operating system. For example, you can use Secure FTP to copy the .csv file into the /home/rsaadmin directory.
Note: This procedure assumes a knowledge of Linux commands. Do not attempt this procedure without the necessary knowledge.
Before you begin
You must have Super Admin and Operations Console administrator privileges to run the User Groups and Token Bulk Requests utility.
You must create an input file that lists all of the bulk requests. For instructions, see Create Input Files for Bulk Requests.
Procedure
Log on to the appliance using an SSH client. For more information, see Log On to the Appliance Operating System with SSH.
Change directories to /opt/rsa/am/utils.
Do the following:
To import bulk token requests, type:
./rsautil import-bulk-request -u admin_UserID -o oc_admin_UserID -f /home/rsaadmin/TokenRequests.csv -r TOKEN
where
admin_UserID is the user name for the Super Admin running the utility.
oc_admin_UserID is the user name for an Operations Console administrator.
/home/rsaadmin/TokenRequests.csv is the request input file (CSV) with pathname and filename.
TOKEN is the request type.
To import bulk on-demand tokencode service requests using the mobile device delivery method, type:
./rsautil import-bulk-request -u admin_UserID -o oc_admin_UserID -f /home/rsaadmin/TokenRequests.csv -r TOKEN -d SMS
where SMS is the delivery method.
When you import on-demand tokencode service bulk requests, the delivery method follows these guidelines:
You can use only one delivery method for each on-demand tokencode service bulk request.
If you configure one delivery method for the on-demand tokencode service, either mobile device or e-mail, all on-demand tokencode service bulk requests use that delivery method.
If you configure both mobile device and e-mail as the delivery methods for the on-demand tokencode service, you can set the delivery method for on-demand tokencode service bulk requests using the (-d) option flag. If you do not use the -d option flag, the default delivery method is e-mail.
If the CSV file does not contain any on-demand tokencode service bulk requests, the delivery method (-d) option flag is ignored.
For information on configuring delivery methods, see On-Demand Tokencode Delivery by Mobile Phone or E-Mail.
To import bulk user group membership change requests, type:
./rsautil import-bulk-request -u admin_UserID -o oc_admin_UserID -f /home/rsaadmin/GroupRequests.csv -r GROUP
where
admin_UserID is the user name for the Super Admin running the utility.
oc_admin_UserID is the user name for an Operations Console administrator.
/home/rsaadmin/GroupRequests.csv is the request input file (CSV) with pathname and filename.
GROUP is the request type.
When prompted, enter the Super Admin and Operations Console administrator passwords.
Note: Although it is possible to enter the Super Admin and Operations Console administrator passwords on the command line along with the other options, this creates a potential security vulnerability. RSA recommends that you enter passwords only when the utility presents a prompt.
Related Concepts
Related Articles
Create Input Files for Bulk Requests 22Number of Views CSV Format for Token Requests Input File 15Number of Views RSA Governance & Lifecycle - sap2csv: Export SAP Tables into csv files 12Number of Views Add a Security Domain 31Number of Views "Access Denied" error when attempting to view detailed information on the RSA Via Lifecycle and Governance Users page 68Number of Views
Trending Articles
Downloading RSA Authentication Manager license files or RSA Software token seed records Unable to login to RSA Authentication Manager Security Console as super admin RSA Authentication Manager 8.9 Release Notes (January 2026) How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Connection fails to Cloud Authentication Service when connecting through a proxy server from RSA Authentication Manager to…