HttpHostConnectException: Connect to :443 failed: Connection refused: connectĪt .(DefaultHttpClientConnectionOperator.java:151)Īt .(PoolingHttpClientConnectionManager.java:353)Īt .(MainClientExec.java:380)Īt .(MainClientExec.java:236)Īt .(ProtocolExec.java:184)Īt .(RetryExec.java:88)Īt .(RedirectExec.java:110)Īt .(InternalHttpClient.java:184)Īt .(CloseableHttpClient.java:82)Īt .(CloseableHttpClient.java:107)Īt .(CloseableHttpClient.java:55)Īt .(BaseUrlHealthCheck.java:53)Īt .(AbstractSupportHealthCheck.java:23)Īt .(PluginSuppliedSupportHealthCheck.java:51)Īt .run(Unknown Source)Īt .runWorker(Unknown Source)Īt $n(Unknown Source)Ĭaused by: : Connection refused: connectĪt (Native Method)Īt (Unknown Source)Īt (Unknown Source)Īt (Unknown Source)Īt (Unknown Source)Īt (Unknown Source)Īt (Unknown Source)Īt .(SSLConnectionSocketFactory.java:337)Īt .(DefaultHttpClientConnectionOperator. Looking into the logs I get this stacktrace : 10:14:15,657 HealthCheck:thread-5 ERROR ServiceRunner An error occurred when performing the Base URL healthcheck: Now I can connect from outside the company's network but I cannot connect from the inside and the base URL gadget check fails. I modified the server.xml use Atlassian guidelines adding these attributes to the Connector node :Īnd added the certificate to the java cacert. We created a URL and added a F5 in front of the network. Hence, full URL would help.We have a jira instance and we want to let people outside of the company network connect to it. But the error message does complain about scopes, so maybe it is some other parameter mismatch. Specifically, prompt=consent is not part of the OAuth 2.0 standard so I’m not sure how Azure would know to send it. What I suspect is that Azure is not aware of all the query string parameters needed by Atlassian. How you need to enter this information depends on the specific IdP. Hitting Next to continue the process right after Step 2, you will be prompted to paste the metadata information from SAML Sign On for Jira in the IdP configuration. If you are getting redirected to, please post the full URL here so we can diagnose further. First: Load Metadata from SAML SSO for Jira into your Identity Provider. Maybe you could find out which authorization flow it wants, and I can open a feature request. And, in that case, we’re stuck because our side only supports the authorization code flow right now. If that’s true, then I would expect Azure never redirects you, in the browser, to that URL. One possible problem is Azure’s OAuth client assumes some flow other than the authorization code flow (also known as 3LO). Welcome to the Atlassian developer community, can think of 2 possible problems, both of which center on how external clients would use the authorization URL. Scopes: Īny guidance would be greatly appreciated.
0 Comments
Leave a Reply. |