|Applies To||Java Authentication API version 5.0.3 Build 172 and earlier.|
|Issue||Successful confirmation authentication after PIN accepted with Java Auth API|
Confirmation authentication following new PIN acceptance is sometimes directed to another Auth Manager in the realm resulting in access denied.
|Cause||The new PIN value has not been replicated to all Authentication Manager replicas. The Java Auth API randomly selects which Server the confirmation authentication is directed to.|
|Resolution||A hotfix is available for this issue. Please contact RSA Customer Support and request hotfix Id73118. |
The authapi.jar from the hotfix package can be used as a drop-in replacement for the authapi.jar being used in your current environment.
|Legacy Article ID||a38232|