000021854 - If Sd_UnassignToken is used to unassign a replaced token in RSA ACE/Server  a database inconsistency appears

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 Number000021854
Applies ToRSA ACE/Server 5.2
RSA Authentication Manager 6.0
Microsoft Windows 2000
Microsoft Windows Server 2003
Sun Solaris
IssueIf Sd_UnassignToken is used to unassign a replaced token in RSA ACE/Server, a database inconsistency appears
Sd_UnassignToken seems to corrupt or otherwise adversely affect the ACE/Server
Database administration, sdadmin, GUI becomes unresponsive after trying to edit a token replaced and unassigned through RSA ACE/Server Administration API
ResolutionIf the RSA ACE/Server GUI becomes unresponsive after trying to edit a token unassigned through an application that uses our Administration API, it's likely that you will experience this problem. The problem is solved by installing RSA ACE/Server 5.2 patch 1. If you are running RSA Authentication Manager 6.0.1, contact RSA Security Customer Support to obtain hot fix ID16049 which is available for Windows and Solaris. From the Readme file:

Hot fix Id16049
==============

This hot fix fixes an issue with Sd_UnassignToken().

Calling this function on a token which was previously replaced, creates a DB inconsistency and other GUI-related side effects.

This hot fix should be installed on Authentication Manager 6.0.1 only. In order to solve this issue on ACE/Server 5.2 install ACE/Server 5.2 patch 1, which can be obtained from RSA SecurCare Online.

Install the hot fix by replacing apidemon in the ACE/utils/toolkit subdirectory.

Contents:

apidemon.exe     APIdemon for Win32 platform
apidemon         APIdemon for Solaris
Legacy Article IDa25418

Attachments

    Outcomes