Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

Renewed TLS Certificates - but browser still shows older one

avatar
Contributor

i have renewed the tls certificates and applied on the cloudera manager server but the browser is still showing the older one by looking at the expiry date , tried clearing the browser cache , but still it shows older ones. appreciate for any help

1 ACCEPTED SOLUTION

avatar

Yes of course.Restart the scm and agents.Then two things can happen:

 - everything falls apart - your agents will not be able to communicate with the scm server

 - all ok - check your certificate with openssl  - if it is still old, you are configuing the certificate in the wrong path.

 

Check also your settings in /etc.

 

View solution in original post

11 REPLIES 11

avatar
As far as I know there is no way to extend the TLS certificate validity, so if you created a new certificate, and placed into a truststore make sure the old one is removed.

avatar
Contributor

@Tomas79

i meant i have requested for an new certificate and applied it on the server

avatar
You can try to get the server certificate via openssl command:
openssl s_client -connect <host>
and verify if the certificate is new or old.
If it is new, then your browser or PC has some issues.

avatar
Contributor

@Tomas79,

 

openssl s_client connect is reading the old certificate ,whereas i have replaced ceritificates with new one under the /opt/cloudera/security/x509 and /opt/cloudera/security/jks path

 

and i did not happen to notice any heartbeat issue , agents hearbeat are also working fine , i don't see any issues with that

avatar
Contributor
Does it require an restart of the cloudera manager service ?

avatar

Yes of course.Restart the scm and agents.Then two things can happen:

 - everything falls apart - your agents will not be able to communicate with the scm server

 - all ok - check your certificate with openssl  - if it is still old, you are configuing the certificate in the wrong path.

 

Check also your settings in /etc.

 

avatar
Contributor

@Tomas79

 

it should have fallen apart after 15 secs, thats interval at which agents sends heartbeat and i have encountered issues with TLS over the past and when somethig has gone wrong , service would immediately fail and throws error in the log.

 

this is quite weird though

avatar
Contributor
i could only see new certificate applied on hue UI, hence i'm pretty sure on the path too of other server

avatar
But Hue does not have to be configured the same way as CM. Every component can have his truststore and keystore configured in a different path. Also for example Hue requires "cert" file in PEM format, other components requires JKS - truststores and keystores.