000013136 - Authentication Manager 7.1- Token import Job fails with an error and 0 tokens imported

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

Article Content

Article Number000013136
Applies ToRSA Authentication manager 7.1 on all supported platforms
Appliance 3.0
IssueSuccessfully import the Tokens in Authentication Manager 7.1

When importing a token in Authentication Manager 7.1, import job finishes with an Error and no tokens get imported. Import Job summary shows:


Import Job Basics 
 Import Job Name:                                  ImportTokens_20090507_1535PM
 Submitted On:                                       05/07/2009 15:35PM
 Submitted By:                                        admin
 Completed On:                                      05/07/2009 15:35PM
 
Imported Tokens 
 Imported file:                                          666706-10-1_token.xml
 Number of tokens imported:                   0
 Number of duplicate tokens imported:   0
 Number of duplicate tokens ignored:     0


 


Administrator Activity log shows Error: "AM_IMPORT_TOKEN_XML_DATA_CORRUPT"

AM_IMPORT_TOKEN_XML_DATA_CORRUPT

Cause

When importing a token in Authentication Manager 7.1 a password field is available in case the seed records are encrypted with password. If you try to import the tokens without entering the password or an incorrect password, the import job will proceed however will finish with an error. The Job summary doesn't indicate that a password was required or the password entered was incorrect.


 It is also possible a particular seed record does NOT need a File Password, but if you add a password you will get the same problem.

ResolutionTo successfully import the tokens, enter the correct password in the password field and the import job will finish successfully. If you think the pasword is correct, try again without a File Password.
NotesA way to test and see if the seed records require a password to import is to try and import the tokens in Authentication Manager 6.1. If the seed records are password protected, you will be prompted for a password and cannot continue the import job without supplying the password.
Legacy Article IDa45918

Attachments

    Outcomes