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
Unable to make a successful Web Service API createChangeRequest call from a Workflow in RSA Identity Governance & Lifecycle Number of Views In RSA Identity Governance and Lifecycle, the Vaild Reply Answers are not displayed in the Approval Request email. Number of Views The approval workflow isn't working as expected when grouping by business source in the request form with the provisioning… Number of Views Upgrade from 7.2.1 or earlier version to SecurID Governance & Lifecycle 7.5.0 or later version stalls at step ACM-102799.sql Number of Views Troubleshooting integrations with the RSA ID Plus Cloud Access Service (CAS) that stopped working following the CAS Entrus… Number of Views
Don't see what you're looking for?
