000021899 - How to Bulk Load Token requests in RSA SecurID Web Express 1.2

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000021899
Applies ToRSA SecurID Web Express 1.2
Microsoft Access
IssueHow to Bulk Load Token requests in RSA SecurID Web Express 1.2
ResolutionInstructions for loading in bulk can be found in the Installation & Configuration Guide (install_config_win.pdf), page 23. Below is the Access database sample:

Loading Token Requests in Bulk

Instead of requiring requesters to submit token requests individually, you can load

requests into Web Express in bulk. The next procedure tells you how to do this. The

specific steps vary depending on the database you are using (either Microsoft Access,

or a third-party database).

To load requests in bulk:

1. Submit a request for a new token in Web Express, but do not process the request.
This request sets the order of the request information in the request database. In

the next step, you use the request database to create a template that will contain the bulk requests.

2. Open the Web Express request database (RSATransaction.mdb), and export the contents into a comma separated value (CSV) file.

For instructions, see the documentation provided with your particular database. This creates a template that will contain the bulk requests.

3. Create a CSV file of the bulk requests, and order the information according to the
template you created in the previous step.

4. Import the CSV file containing the requests into the Web Express request


Sample request:


15rsatest2rsatest2rsatest2Testtest@test.comNoneHardware_fobTokenTypeHardware_fobYesAwaiting_ApprovalMar 28, 2005 at 02:03 PM EST            

There are several key fields to be focused on:

1. Request_Number. This must be incremented by one for each new request.

2. All fields populated by the initial request in Item 1 from the instructions must be populated down for each token request entry

Legacy Article IDa25656