Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Microsoft Azure Active Directory SSO for Jira Add-on has incorrect pre-populated setup data

Jae An
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 10, 2018

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?


1 answer

0 votes
Knut Arne Ristebråten November 27, 2018


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="<>" proxyPort="<proxy_port>" secure="true"

Se step 9 on the following documentation:

Hope this helps.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events