How to correctly utilize the RSASecurIDAuthenticationEngine.resynch method
Originally Published: 2006-08-30
Article Number
Applies To
Issue
SAE Javadoc mentions possible return value of NEXT_CODE_REQUIRED but does not describe required action when this status is returned.
Resolution
Providing the two consecutive tokencodes minimizes the possibility of incorrectly setting the token's offset and causing subsequent authentication errors.
Related Articles
What are the token windows used for Event-based tokens? Number of Views Error message "Error: java.lang.IllegalArgumentException: Window boundary must be positive" in the RSA SecurID Authenticat… Number of Views How to set PINs and navigate Next Tokencode Mode for RSA SecurID Tokens using NTRadPing Number of Views RSA Authentication Manager 8.8 Administrator's Guide Number of Views RSA Authentication Agent for Web: IIS Authentication Test Fails Due to Node Secret Mismatch with RSA Authentication Manager Number of Views
Trending Articles
RSA Release Notes for RSA Authentication Manager 8.8 RSA Authentication Manager 8.9 Release Notes (January 2026) When running "acm startdb" or "service aveksa_server startdb" for RSA Via Lifecycle & Governance the error "PRCD-1027 : Fa… RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA Authentication Manager Upgrade Process
Don't see what you're looking for?
