000011964 - Cannot log in to Security or Operations Console after SP2 upgrade

Document created by RSA Customer Support Employee on Jun 14, 2016•Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • Comment • 0
  • View in full screen mode

Article Content

Article Number000011964
Applies ToRSA Authentication Manager 7.1 SP2
SecurID Appliance 3.0
IssueCannot log in to Security or Operations Console after SP2 upgrade
System Internal Error
Security Console will not open

System internal error, there was a problem processing your request, please contact your system admin


Cannot log into Operations Console
Security Console shows no login

[weblogic.servlet.internal.WebAppServletContext@d72ac9 - appName: 'console-ims', name: 'console-ims.war', context-path: '/console-ims'] Servlet failed with Exception java.lang.NoClassDefFoundError: com/rsa/ui/common/security/csrf/shared/NonceManager


<User defined listener com.rsa.ui.common.security.csrf.CSRFSessionListener failed: java.lang.NoClassDefFoundError: com/rsa/ui/common/security/csrf/shared/NonceManager. java.lang.NoClassDefFoundError: com/rsa/ui/common/security/csrf/shared/NonceManager

CauseInstalling the SP2 patch as a different user than the original install sometimes causes the config.xml to fail to be updated correctly. The Operations Console Administrators are also not migrated and will need to be recreated.
Resolution

On an Appliance 3.0:
To restore the Security Console:

1. Open an SSH session and login as emcsrv
2. Issue the following commands:

sudo su - rsaadmin
cd /usr/local/RSASecurity/RSAAuthenticationManager/server
./rsaam stop all
cd /usr/local/RSASecurity/RSAAuthenticationManager/server/config
cp config.xml configbackup.xml
cd /usr/local/RSASecurity/RSAAuthenticationManager/utils
./rsautil manage-config -a regenerate
cd /usr/local/RSASecurity/RSAAuthenticationManager/server
./rsaam start all

Once services are started you should be able to log in to the Security Console.

To Restore the Operations Console:

1. Open an SSH session and login as emcsrv
2. Issue the following commands:

sudo su - rsaadmin
cd /usr/local/RSASecurity/RSAAuthenticationManager/utils
./rsautil manage-oc-administrators -a create

You will be prompted for Super Admin credentials, then for a new OC admin username and password. Once this user is created use it to log in to the Operations Console

 


In Windows:   To restore the Security Console:

1. Stop RSA services
2. Backup the config.xml located in:  c:\Program Files\RSA Security\RSA Authentication Manager\server\config
3. Change directory to the utils directory:  cd c:\Program Files\RSA Security\RSA Authentication Manager\utils

4. Run the following command: rsautil manage-config -a regenerate

5. Start RSA services
Once services are started you should be able to log in to the Security Console.

 

To Restore the Operations Console:

1. Change directory to the utils directory:   cd c:\Program Files\RSA Security\RSA Authentication Manager\utils
2. Issue the following command:    rsautil manage-oc-administrators -a create

You will be prompted for Super Admin credentials, then for a new OC admin username and password.
Once this user is created use it to log in to the Operations Console

 

NotesLog messages above are located in:
Windows:
c:\Program Files\RSA Security\RSA Authentication\ Manager\server\servers\<machine name>_server\logs\<machine name>_server.out
Appliance:
/usr/local/RSASecurity/RSAAuthenticationManager/server/servers/<machine name>_server\logs\<machine name>_server.out
Legacy Article IDa48415

Attachments

    Outcomes