ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

After upgrade, on SSL enabled environment, beacon does not deploy with error "Keystore was tampered with, or password was incorrect"


Article ID: 199149


Updated On:


Clarity PPM On Premise Clarity PPM SaaS


After a successful upgrade, unable to bring up CSA or application or connect to Clarity

When deploying services, error is thrown:

Caused by: Keystore was tampered with, or password was incorrect

Caused by: Password verification failed



Issue is due to a wrongly set up SSL keystore.


Release : Any



Check CSA or properties.xml to ensure the ssl keystore is set up properly.

If it's not set up correctly:

  1. Update the keystore and its password correctly
  2. Save
  3. Redeploy the services

If you cannot find anything obviously wrong with it, try removing the keystore option and redeploy:

  1. On line 23 of the properties.xml if you see something like this:
    <ssl keystore="" password="password"/>
    Please update it to make it look like this: 
    <ssl keystore=""/>

  2. Open $Clarity/config folder and look for a file called .keystore. Make sure your files are unhidden. If you have one, remove it and place it somewhere else outside of Clarity directory
  3. Save and redeploy the services. See if you get any more errors in the beacon log and how the services come up.
  4. If the services come up correctly, the SSL keystore has to be regenerated and updated