Hi, I've noticed a 'Trusted Client CA' Certificate has a warning in the log stating "Certificate 'XXXXX' is about to expire within next 60 days" but if I check the certificate the end date is years away 2114. If I run the certificate validity checker it says it will expire end of next month. This cert is for authentication so important to understand why the date is not as per the end date on the cert?
It was around this time last year when I imported this CA cert so could it be the trusted client CA certs have a max 1 year validity irrespective of what is on the actual cert. :/
I always find dealing with Certificates is a 'Dark Art' so if anyone has seen this before be useful to know, Cheers.
Solved! Go to Solution.
FYI - Pulse have released KB45235 to address this certificate validity problem, the KB states the 'Trusted Server CA Shows incorrect validity for EE Certification Centre Root CA' but it can effect other certificates. Its cosmetic only and will be resolved in a later release. thanks.https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB45235/?kA13Z000000X0I4
@zanyterpThanks zanyterp, I've raised a case and support are investigating. Definitely an odd one, the cert checks out all ok using OpenSSL which validates the end date in 2119 all ok. The cert also looks correct within Pulse, it just seems to be the "Certificate Validity Check" within Pulse which is calculating the incorrect end date. Could it be the validity checker is effected by the 2038 Unix time formatting bug. Hopefully support will get to the bottom of it. Cheers
FYI - Pulse have released KB45235 to address this certificate validity problem, the KB states the 'Trusted Server CA Shows incorrect validity for EE Certification Centre Root CA' but it can effect other certificates. Its cosmetic only and will be resolved in a later release. thanks.https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB45235/?kA13Z000000X0I4