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
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
Error message "Illegal TXN State: Attempt to start new transaction during rollback" in RSA Identity Governance & Lifecycle Number of Views RSA Via Lifecycle and Governance Workflow fails with error "Illegal TXN State: Attempt to start new transaction during rol… Number of Views Failed RSA SecurID Authenticate tokencode authentication attempt to RSA SecurID Authentication Manager causes two failures… Number of Views Setting New Pin when using RADIUS in a LoadBalancer environment usually fails Number of Views Attempts to scrub/hash JSON data elements are not always working in RSA Web Threat Detection Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide How to Download OTP Token Seed Files from myRSA How to factory reset an RSA Authentication Manager 8.x hardware appliance without a factory reset button from the Operatio… RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?
