Azure-docs: Running jira behind reverse proxy

[arnrist]

When running Jira behind a reverse proxy, the URL's for Identifier, Reply URL and Sign On URL in "Microsoft Azure Active Directory single sign-on for JIRA" gets listed in http and not https, which again cases the setup to fail in Jira due to "Invalid Reply URL".
As described on https://community.atlassian.com/t5/Answers-Developer-Questions/Connecting-JIRA-to-Azure-AD/qaq-p/573166

Please correct this. The Jira instance is running behind Apache Proxy that have https towards clients, but the proxy between Apache and Jira is http.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: d38cad90-6574-38c2-3262-059a9f975064
• Version Independent ID: dd08d5c5-65a4-c2cc-8b51-7a35268dde68
• Content: Tutorial: Azure Active Directory integration with JIRA SAML SSO by Microsoft
• Content Source: articles/active-directory/saas-apps/jiramicrosoft-tutorial.md
• Service: active-directory
• GitHub Login: @jeevansd
• Microsoft Alias: jeedes

[SaurabhSharma-MSFT]

@arnrist Thanks for the feedback ! I have assigned this issue to content author to investigate and update the document as appropriate.

[martin1856]

We are seeing the same problem. We have JIRA behind a load balancer setup for SSL Offload. In our case, the URLs for Reply URL, Identifier, and Sign On URL are all coming up as http instead of https.

[megamorf]

We are affected as well. Our jira instance runs behind a Traefik reverse proxy that does SSL termination and the SSO plugin's settings only show http based endpoints instead of https.

[jeevansd]

@megamorf and @martin1856 We are going to provide some option as a workaround on this issue. In the next month we will provide some work around on this issue.

[martin1856]

That’s great news! Thanks!

Dan Martin

[danilo-nlima]

Having exactly the same problem, Waiting for any workaround as well...

[dougcain]

Same issue: tells me I have “Invalid Reply URL” and “Invalid Sign On URL”

[jusefb]

Having the same issue

[jeevansd]

@dougcain and @jusefb We are working on this change and will publish the update to the plugin in a week or two. Please hold on!

[jusefb]

@jeevansd perfect, thank you for the update

[jusefb]

Hi, it has been almost a month. Any update on the progress of this issue?

[jeevansd]

@jusefb We are already trying this solution with a customer. If you want to also give a try please send us the email on [email protected] Then we can work with you.

[jusefb]

I have sent you an email, let me know the next steps. The email would be from [email protected]

[jeevansd]

@jusefb Done already. Please check the email.

[jusefb]

Hi, thanks for this. We have decided to go with Jira cloud so will not be needing this solution anymore I guess. Thank you for all your help

[jeevansd]

@jusefb In that case you should be using the Atlassian Cloud app from Azure AD app gallery. The cloud version comes with the built in SAML support.

[tico24]

Hi @jeevansd, we would love to help test the solution with you as this issue is blocking a jira rollout for us at the moment. I emailed about 2 weeks ago, but can email again if you like?

[jeevansd]

@tico24 The doc should get updated by today sometime. So please check the doc tomorrow and you should see the instructions on how to configure this.

[arnrist]

I've updated my XML file as described in step 9 a on the new docs, and can confirm that the setup is now working! After XML update, the Reply and SignOn URL is listed with https.

Thank you for presenting the solution.

[martin1856]

This worked for us as well. Any way to default login to use the Azure SSO, instead of forcing the user to click the button for Azure to login?

[jeevansd]

@martin1856 and @arnrist Thanks for the confirmation.
For forcing the Azure AD login I can take this as a feature request to our plugin. Thanks for your input.

[jeevansd]

Document is updated now.

please-close