Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-42476

More Verbose Error on UI When Create Application Link Fails

    XMLWordPrintable

Details

    • 2
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      When Jira Cloud fails to create an application link, we should have more details as to why the application link fails to create.

      Currently on the UI we display:

      No response was received from the URL you entered. It may not be valid.

      or

      No response was received from the URL you entered - it may not be valid. Please fix the URL below, if needed, and click Continue.

      While the Cloud logs will tell us:

      javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
       at com.sun.mail.imap.IMAPStore.protocolConnect(IMAPStore.java:441)
       at javax.mail.Service.connect(Service.java:233)
       at javax.mail.Service.connect(Service.java:134)
      Unable to respond to any of these challenges

      and so on. Including even these errors messages on the UI would be extremely useful.

      Server side logs will show this on trying to create the application link:

      YYYY-MM-DD 12:14:46,709+1300 JIRA-EventThread-225 WARN username 734x13917x1 ghdyd1 0:0:0:0:0:0:0:1 /rest/applinks/3.0/applicationlinkForm/manifest.json [c.a.a.internal.capabilities.DefaultRemoteCapabilitiesService] Exception trying to get Applink for manifest with ID c...

      To diagnose further, openssl test can be performed to verify the SSL is configured correctly in Jira via the following command (preferably from anothermachine:

       openssl s_client -connect jira.server.hostname:443
      

      Expected results
      The command should return no errors regarding certificate chains.

      Actual results
      Something like below will be displayed:

      CONNECTED(00000003)
      depth=0 CN = *.ihostname
      verify error:num=20:unable to get local issuer certificate
      verify return:1
      depth=0 CN = *.ihostname
      verify error:num=21:unable to verify the first certificate
      verify return:1
      

      Same can also be confirmed by running a check from a 3rd party SSL checker, for example:
      https://www.ssllabs.com/ssltest/analyze.html?d=your.host.name

      The checks shouldn't return any missing certificates.
      Something like below will indicate that there's an issue with SSL at the JIRA server side:

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              bcruz@atlassian.com Brian Cruz (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: