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
Utilize AMBA EODA command ExpiryDate parameter Number of Views RSA Security Advisories Severity Rating Number of Views How to properly utilize Citrix NetScaler load balancer to work with the RSA Authentication Manager 8.1 SP1 Web Tier Number of Views Upgrade fails with "A newer version of RSA Identity Governance and Lifecycle has already been installed" Number of Views Unable to make a successful Web Service API createChangeRequest call from a Workflow in RSA Identity Governance & Lifecycle Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA Authentication Manager 8.9 Patches and Hotfixes Readme Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU Authentication Manager Security Console and Operations Console Inaccessible After Certificate Update Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory
Don't see what you're looking for?
