You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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?
Hi,
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.