CertificateTooOldException when Configuring Trusted Applications Authentication on an application link
Setting up Trusted Applications authentication on an Application Link between JIRA and another application may fail with the exception below. In some cases, this error is logged but trusted communication is working.
Failed to login trusted application: confluence:14159892 due to: com.atlassian.security.auth.trustedapps.CertificateTooOldException: OLD_CERT; Certificate too old.
Failed to login trusted application: jira:123213 due to: com.atlassian.security.auth.trustedapps.CertificateTooOldException: Certificate too old.
There is a date/time difference between the JIRA server and the other application server. Most often, the problem occurs after re-starting one of the application's server, whereby the NTP is not timely synchronized, causes an offset. Note that this issue does not affect OAuth authentication.
- Verify the system clocks are identical (to the second). 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 timeout or put zero timeout value as per our Configuring Trusted Applications Authentication for an Application Link documentation.
- Use OAuth instead of Trusted Applications Authentication for the Application Link.