We are currently evaluating Jira, and I am trying to setup our Azure AD to be integrated with Jira for SSO. However, the Add-on (Microsoft Azure AD SSO for Jira) configuration option shows pre-populated setup information (Identifier, Reply URL, Sign On URL) that do not match with our system. For instance, our system is SSL enabled, and all URL should have "https://", but the pre-populated setup has "http://" addresses.
Using the Federation Metadata URL from Azure correctly populates other setup fields with "https://", but it would not change the incorrect default value or allow me to manually change them either.
Any idea what may be causing this problem?
I reported a bug on this, and Microsoft have updated their documentation today. I've tested the solution that it does work.
The issue occurs when you run behind a reverse proxy, you need to add the below attribute in connector port in server.xml file of Jira:
scheme="https" proxyName="<subdomain.domain.com>" proxyPort="<proxy_port>" secure="true"
Se step 9 on the following documentation: https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/jiramicrosoft-tutorial
Hope this helps.
For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events