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

[Jae An]

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?

[Knut Arne Ristebråten]

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.

[Aleksandar Salevski]

Hi Knut,

I set up these attributes in server.xml for conf, restarted Jira, still Reply find Sign in URL are showing HTTP instead of HTTPS, we are running Confluence on VPN, do you think that might be a problem?