If you run Jira behind a http proxy, namely https (ssl) then you need to add three options to the server.xml file in /opt/atlassian/jira/conf:
The only change needed to vanilla Jira. Then in something like nginx you have the line:
SImple you would think but there are a few steps more than what you may first think to getting SSO through Windows Azure Active Directory working.
Next you need to install Active Directory Federated Services. You do this through Server Manager->Roles on your WSE box. The go to the flag in Server Manager and select the post deployment details. Follow the wizard creating new managed service user and creating the KDS root key as instructed.
Install the Windows Azure Active Directory Module. You will also need the Microsoft Online Services Sign-In Assistant for IT Professionals BETA module too. Install .net 3.5 through roles and features.
In my case I had an already confirmed domain but I needed to convert this to Federated for SSO. Use Connect-MsolService with the organizational account for your domain and then the Convert-MsolDomainToFederated –DominaName “domain.tld”
In Windows Azure you should confirm that the domain name is now marked as verified and is configured for SSO.
Log off and log back on again – actually I did a restart to install updates.
Then download dirsync and install on your local WSE.
After running it you should all be in sync. If you change identities used for the sync then you’ll need to run the tool again.
vim-cmd vmsvc/power.shutdown ID
esxcli system maintenanceMode set -e yes
esxcli software vib update –dry-run -d http://vibsdepot.hp.com/index.xml
esxcli software vib install –dry-run -d http://vibsdepot.hp.com/index.xml
esxcli system maintenanceMode set -e no