000022164 - Replacement SecurID token appears twice  and the replaced token is not removed in RSA ACE/Server

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 Number000022164
Applies ToRSA Authentication Manager 6.0.2
RSA ACE/Server 5.1.2 (no longer supported as of 7-14-2006)
RSA ACE/Server 5.1.1 (no longer supported as of 7-14-2006)
UNIX (AIX, HP-UX, Solaris)
Microsoft Windows Server 2003
Microsoft Windows 2000 SP4
Authenticating with the replacement token should remove the original (replaced) token and leave just one entry for the replacement token, now marked as the original
IssueReplacement SecurID token appears twice, and the replaced token is not removed in RSA ACE/Server
Users are unaware of the issue, and can authenticate through RSA ACE/Server
ResolutionThis problem has been corrected in a hot fix for RSA ACE/Server 5.1.2. Contact RSA Security Customer Support and request the hot fix ID18099.

NOTE: For RSA Authentication Manager 6.0.2 running on Solaris request hotfix ID24772 (agent authentication) and ID23746 (remote admin authentication)

This issue is caused by the ACE/Server not removing the token extension data for the original token. When the replacement token tried to delete the original token, the request was rejected because token extension data was still present.
Legacy Article IDa27174

Attachments

    Outcomes