CertificateTooOldException when Configuring Trusted Application Link
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
Setting up Trusted Communication between Bitbucket Server and JIRA may fail with the exception below:
1
2013-12-09 08:25:35,815 http-bio-80-exec-3896 WARN anonymous 505x1037338x2 - 10.0.18.77 /rest/api/2/search [auth.trustedapps.filter.TrustedApplicationFilterAuthenticator] Failed to login trusted application: 0A00124D01405B0743A26A350C02BC37 due to: com.atlassian.security.auth.trustedapps.CertificateTooOldException: Certificate too old. Application: 0A00124D01405B0743A26A350C02BC37 Certificate Created: Mon Dec 09 08:23:59 EST 2013 Timeout: 10000Cause
There is a date/time difference between the Bitbucket Server instance and JIRA server. The problem usually occurs after re-starting one of the application's server, whereby the NTP is not timely synchronised thus causing an offset.
Resolution
Verify the system clocks are similar. If the servers are in different timezones, ensure that their OS timezones are set correctly. Use a NTP time server if you're finding the clocks are going out of sync very often.
Increase the Certificate Timeout (ms) value as per our Configuring Trusted Applications Authentication for an Application Link documentation.
Was this helpful?