000015056 - Getting initialization page when accessing /KMS after an RKM Appliance installation

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

Article Content

Article Number000015056
Applies ToRSA Key Manager Appliance 1.6.1
IssueGetting initialization page when accessing /KMS after an RKM Appliance installation
ResolutionIf you get to the initialization page (install.jsp) when hitting /KMS on the appliance right after install this means that the initialization failed for some reason.

To get the real reason, do the following:

Provide the same master password that you provided during install.
Database username : local
Database password : Provide the master password
Authentication type : Select Access Manager
Access Manager username : kmsadmin
Access Manager host : localhost
Access Manager port : 5608
Timeout : 90

Click initialize. This should give you the error.

In this specific case, the error returned was "JDBC username/password invalid", so we did the following:

Log in as root on the primary appliance, and ran:
  su - oracle
  sqlplus / as sysdba
  SQL> alter user local identified by <masterPassword>;
  SQL> exit
  exit
Delete all files except keymanager.properties in the folder /opt/KMS/conf/properties
Restart Tomcat
  service tomcat restart
Hit /KMS with a browser
Provide the same values to the initialization page as above
This time the init worked.

Now we had to modify the standby as well. Since the DB on the standby is in MOUNTED state (not open), we can't modify the user password, so you have to do a manual switchover from the Operation Console:
  Hit /rkmawa with a browser on the standby, go to Operations --> Clusters, and click on Make Primary to make the standby the new Primary.

Once the switchover is complete, go back on the primary and run:
  cd /opt/KMS/conf/properties
  scp databaseCredentials.properties softwareMasterKey.properties unattendedRestart.properties accessManager.properties <hostnameOfStandby>:`pwd`

Now log in as root on the standby and run:
  su - oracle
  sqlplus / as sysdba
  SQL> alter user local identified by <masterPassword>;
  SQL> exit
  exit

Restart Tomcat: service tomcat restart
Hit /rkmawa with a browser and switch back the roles to their original roles.
Legacy Article IDa47610

Attachments

    Outcomes