Issue :
After upgrading, users are unable to log in to the Applications Manager Plugin. Both auto sign-in and manual login fail. When accessing the Applications tab in the OpManager UI, it redirects to the Applications Manager login page instead of automatically logging into the Plugin.

Note: This issue would occur when Applications Manager is upgraded to version 17000X.
Reason :
The issue likely occurs due to permission-related problems that prevented the latest Tomcat folder from being copied during the upgrade.
Log traces:
Please refer to the log traces found in the Applications Manager logs to confirm if the issue is related to a Tomcat upgrade failure.
In StartUpLogs_out.txt,
[10:21:12:362]|[10-14-2024]|[STARTUP_OUT]|[DEBUG]|[1]: Tomcat Version used in our product is :: 9.0.70|In localhost_access_logs,
10.163.58.16 - - [14 Oct 2024 10:29:05:472] "POST /j_security_check HTTP/1.1" Response code:500 Size(bytes):- Time(sec):0.002 Thread:https-jsse-nio-8443-exec-7Solution :
If the folders /working/apache/tomcat_9_0_70 or tomcat_9_new are present, move them manually to the required location.
Linux & Windows :
Steps to Resolve:
Rename the existing Tomcat folder:
- Rename the existing
/working/apache/tomcat
folder to tomcat_old_9
.
Rename the new Tomcat folder:
- Rename the
/working/apache/tomcat_9_0_70
or tomcat_9_new
folder to /working/apache/tomcat
.
Transfer important files from the old Tomcat folder to the new one:
- Copy the
appmanager.keystore
file from the old Tomcat folder (tomcat_old_9
) to the new Tomcat folder (/working/apache/tomcat
). - Copy the
/working/apache/tomcat/conf/backup
folder from the old to the new Tomcat folder. - Copy the
/working/apache/tomcat/webapps
folder from the old to the new Tomcat folder (for CAS SSO support).
Update server.xml
:
- Review the old
server.xml
file and copy any custom KeystoreFile
and TrustStoreFile
entries from the old Tomcat folder to the new one. - If applicable, review the old ciphers from
server.xml
and update the new file to include ciphers for TLSv1.3 (optional).
Restart the OpManager Service:
- After completing the above steps, restart the OpManager service.
Verification:
- After the restart, verify that the login issue in the Applications Manager Plugin is resolved.

Ensure all required files and configurations are moved correctly from the old Tomcat folder to the new one before restarting the service.
By following these steps, the login issue caused by the failure to copy the latest Tomcat folder during the upgrade should be resolved.