000019001 - How to disable SecurID Tokens before they go into Next Token Mode

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 Number000019001
Applies ToRSA ACE/Server 4.1 (no longer supported as of 2-1-2004)
UNIX (AIX, HP-UX, Solaris)
IssueHow to disable SecurID Tokens before they go into Next Token Mode
CauseAfter a set number of bad passcodes a SecurID Token will be put into Next Tokencode.  If the next Token code fails the Token will then be disabled in the ACE/Server.  The aim is to disable tokens after a certain number of bad passcodes without sending them into Next Tokencode Mode
ResolutionOn the ACE/Server for NT, this can be configured without a problem. However on UNIX there is an error in sdsetup -config which stops you from changing Token behaviour.

This has been fixed in Patch 3 for ACE/Server 4.1.
Install patch 3, restart the ACE/Server and run sdsetup -config to change parameter. Redistribution of sdconf.rec to the Slave and Agents is not necessary.
Legacy Article IDa4827

Attachments

    Outcomes