If the eserver drops a connection to the selfservice console the selfservice console does not attempt to reestablish a new connection
Originally Published: 2011-08-29
Last Modified: 2023-09-25
Article Number
Applies To
Issue
Whenever there is an interruption in the eserver connection to the self service console, the eserver does not attempt to establish a new connection
Cause
Resolution
This is a defect in the selfservice.war file, and is corrected in AxM hotfix 6.1.3.14 or higher. Do to a change in the way jar files are signed you must first be on hotfix 6.1.3.4 or higher to install hotfix 6.1.3.14.
To obtain this hotfix, please contact RSA AxM support, and request hotfix 6.1.3.14 (or the latest selfservice.war hotfix, as all hofixes for each component are cumulative)
Related Articles
RSA Via Lifecycle and Governance Workflow fails with error "Illegal TXN State: Attempt to start new transaction during rol… 263Number of Views How to change username format in Authentication Manager 21Number of Views Archive Requests Utility 6Number of Views "Tokencode is incorrect" while attempting to resynchronize an RSA SecurID software token on RSA Authentication Manager 8.x 185Number of Views Error message "Illegal TXN State: Attempt to start new transaction during rollback" in RSA Identity Governance & Lifecycle 112Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager Patch Updates RSA Authentication Manager Upgrade Process RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities
Don't see what you're looking for?