log files is spoiled with "Failed to login trusted application: confluence ... CertificateTooOldException"

Question

2012-10-15 12:12:37,774 http-8091-20 WARN anonymous 732x86437x1 - 138.203.144.49 /sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml auth.trustedapps.filter.TrustedApplicationFilterAuthenticator Failed to login trusted application: confluence:6775045 due to: com.atlassian.security.auth.trustedapps.CertificateTooOldException: Certificate too old. Application: confluence:6775045 Certificate Created: Mon Oct 15 12:12:27 CEST 2012 Timeout: 10000

2012-10-15 12:12:54,753 http-8091-20 WARN anonymous 732x86472x1 - 138.203.144.49 /sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml auth.trustedapps.filter.TrustedApplicationFilterAuthenticator Failed to login trusted application: confluence:6775045 due to: com.atlassian.security.auth.trustedapps.CertificateTooOldException: Certificate too old. Application: confluence:6775045 Certificate Created: Mon Oct 15 12:12:41 CEST 2012 Timeout: 10000

2012-10-15 12:13:28,809 http-8091-20 WARN anonymous 733x86473x1 - 138.203.144.49 /sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml auth.trustedapps.filter.TrustedApplicationFilterAuthenticator Failed to login trusted application: confluence:6775045 due to: com.atlassian.security.auth.trustedapps.CertificateTooOldException: Certificate too old. Application: confluence:6775045 Certificate Created: Mon Oct 15 12:13:14 CEST 2012 Timeout: 10000

It looks like that when this happen there is performance issue.

Confluence is hosted on the same host.

Priya Ayyadevara · Answer

Hi Adam,

We are on Jira 6.2.7 and Confluence 4.3.7. we tried updating the timeout to 0 but doesn't work.

The Jira gadgets added on confluence pages return no data. They dont prompt an error either. They come up with " The filter for this gadget did not return any issues" . Frustrating as the logs show CertificateTooOldException but both applications are on the same server.

Adam Barylak · Answer

The issue is actually just due to the delay in how long the page takes to load and how long it takes JIRA to respond.  I just ran into this.  If you see in your logs the difference between the time when the warning was logged and the time on the certificate:

* 12:12:37,774 --> 12:12:27 (the response took 774 milliseconds too long)
* 12:12:54,753 --> 12:12:41 (response took 3,753 milliseconds too long)
* 12:13:28,809 --> 12:13:14 (response took 5,809 milliseconds too long)

All you need to do is go into your application link settings, and change the timeout under the trusted applications section to a higher value (default is 10000), or you can set it to 0 which will be no timeout.  Set any higher value, i would definitely go 20000 or higher.

Tiago Comasseto · Answer

Hi Gerard,

CertificateTooOldException message seems related to date/time difference between the JIRA and Confluence. But it sounds strange as you mentioned they are installed on the same server.

Just to be sure, you may want to confirm the date/time at the System Information page of both applications. Alternativelly to this, you can increate the application link timeout. These two solutions are described at this KB.

I hope this helps.