JIRA issue Source tab displays No related source found
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
The JIRA 'Source' tab displays "No related source found" message when integrated with Bitbucket Server.
The following errors are present in the logs:
1
12:50:05,327 WARN [http-bio-8443-exec-3] 770x7480x1 192.168.0.242 "GET /rest/jira/1.0/issues/WR-175246/commits HTTP/1.1" c.a.s.a.t.f.TrustedApplicationFilterAuthenticator Failed to login trusted application: jira:5365394 due to: com.atlassian.security.auth.trustedapps.CertificateTooOldException: Certificate too old. Application: jira:5365394 Certificate Created: Fri Aug 02 12:48:41 EDT 2013 Timeout: 10000Cause
When setting up the trusted application in Bitbucket Server, there is an option to specify the timeout setting. Bitbucket Server will only process trusted application requests from JIRA if they are received in less than the configured timeout period. The timeout period is a preventative measure to protect against replay attacks.
The error above indicates that requests from JIRA are exceeding this timeout. This can be caused by:
Network latency between the servers running Bitbucket Server and the box running JIRA.
Alternatively the system clocks on the boxes are not set to have the same time.
Resolution
Apply the CertificateTooOldException when Configuring Trusted Application Link Knowledge Base.
Was this helpful?