Import Bulk Requests for User Groups and Tokens

Document created by RSA Information Design and Development on Jun 13, 2017Last modified by RSA Information Design and Development on Jun 13, 2017
Version 2Show Document
  • View in full screen mode

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 

  1. Log on to the appliance using an SSH client. For more information, see Log On to the Appliance Operating System with SSH.

  2. Change directories to /opt/rsa/am/utils.

  3. 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 Tokencodes.

    • 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.

  4. 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

Provisioning Overview

 

 


Attachments

    Outcomes