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 the RSACookieAPI function RSAGetUserName on a different host than the (Web Agent-protected) Web Server 9Number of Views Utilize AMBA EODA command ExpiryDate parameter 37Number of Views Deploying RSA Authenticator 6.2.3 for Windows Using DISM 54Number of Views RSA Authentication Manager 8.1 Service Pack 1 Patch 2 Web Tier fails to install 233Number of Views How to properly utilize Citrix NetScaler load balancer to work with the RSA Authentication Manager 8.1 SP1 Web Tier 606Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA Authentication Manager 8.9 Setup and Configuration Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager Patch Updates How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device
Don't see what you're looking for?