Does Jira ver. 6.4.13 & Script Runner 3.1.4 have issue with sslProtocol="TLSv1.1,TLSv1.2,TLSv1.3?

[Tim Burgess]

Cannot connect connect from groovy script to Jenkins https address.  Is there a work around that still uses these protocols?

[Tim Burgess]

There is no error, this is the last thing I see in the Atlassian-jira.log:  018-02-21 12:58:15,220 http-nio-8443-exec-24 DEBUG [invokeJenkinsBuild.groovy] LCM number is LCM-103146
2018-02-21 12:58:15,220 http-nio-8443-exec-24 DEBUG [invokeJenkinsBuild.groovy] SVN_REVISION=HEAD&ISSUE_NUMBER=LCM-103146&DOMAIN=flexC&APPLICATION=PostClosingData&SVN_LOCATION=trunk&MAVEN_BUILD_TYPE=snapshot&RELEASE_VERSION=null&DEVELOPMENT_VERSION=null
2018-02-21 12:58:15,220 http-nio-8443-exec-24 DEBUG [invokeJenkinsBuild.groovy] Jenkins connection code: sun.net.www.protocol.https.DelegateHttpsURLConnection:https://jenkins-XXXXXXX.net/buildByToken/buildWithParameters?job=CLT_HULA/build-decide&token=JIRA   Nothing connects, nothing in the Jenkins logs as well.

[Thomas Deiler]

Dear @Tim Burgess,

if there is an error in the log like:

IOException: sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid
certification path to requested target

than the certificate of the destination host cannot be validated. Therefore you have to add the cert to your trust store java is using.

So long

Thomas

[Tim Burgess]

Thanks, I verified cert is in the trust store.  No exception or error.  Just does not connect.  That is why I think it might be with the above protocols and my Jira version, but would like to know or work around.

[Thomas Deiler]

Dear @Tim Burgess,

how do you know that  there is a problem? what's the error message and where?

So long

Thomas

[Thomas Deiler]

@Tim Burgess, have you tried to connect to something different instead of Jenkins, eg. another web service or just a netcat listener, to see if anything is incoming?

nc -l 443  (done on destination host)

 So long

Thomas