How to correctly utilize the RSASecurIDAuthenticationEngine.resynch method
Originally Published: 2006-08-30
Last Modified: 2023-11-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 How to properly utilize Citrix NetScaler load balancer to work with the RSA Authentication Manager 8.1 SP1 Web Tier Number of Views Workflow variable ${jobUserData_WorkItemURL} doesn't get resolved for email reminder workflow in RSA Identity Governance a… Number of Views RSA SecurID Desktop Token 5.0.3 for Windows Administrator's Guide Number of Views "Error 2004: Cannot locate AMBA license file: ./AMBAlicense.dat " when attempting to run RSA Authentication Manager Bulk A… Number of Views
Trending Articles
Artifacts to gather in RSA Identity Governance & Lifecycle How to Update the Root (Server) and Client Certificates in RSA Identity Governance & Lifecycle How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle How to Download and Reinstall the AFX Server Archive in RSA Governance & Lifecycle
Don't see what you're looking for?
