No secret, I've been working with AzureAD, Office365 Hybird and running Atlassian tools in Azure for some time. I've always published my applications via AzureAD Enterprise Apps to ensure Single Sign On. Sending groups over to Jira and confluence for instance is a bit challenging to do vs ADFS. Partly because in AzureAD user.group is a restricted claim. You can however use the application role claim (user.assignedroles) instead.
So, lets get some prerequisites down for this article.
1. Firefox web browser with SAML Tracer - This nifty tool lets you dive into the saml claim to see what claims are sent and what their values are.
2. Access to AzureAD as an Administrator
3. SAML Single Sign On installed in your application and basically configured following their instructions. I, however I publish my apps as non-gallery applications and use my own custom image tile. This app holds all the magic to convert the role into jira groups.
5. A random GUID generator.
6. Access to the Microsoft Graph Explorer website
7. Groups in AD, synced to AzureAD (or directly in AzureAD) to map user rights to. ie, groups called jira-users, jira-admins, jira-special-role.
Ok, there's no real easy way to get this done other than to start beating at it. We're basically going to follow the Microsoft article and then add the magic Application sauce.
First, In the Azure portal, open up AzureAD and the Enterprise published app for Jira. We need to copy down the Object ID under Properties.
While we're here, lets take a quick peek at the SAML claims I send to jira as well and prep it by adding the group claim.
Now, lets authenticate to the Graph Explorer website. Make sure to login, click modify, to modify your permissions and check Directory.AccessAsUser.All, Directory.Read.All, Directory.ReadWrite.All. Then click the modify permissions button.
Once logged in, try a query. Select GET, change Version from 1.0 to beta, enter the following string and click run query.
If you're successful, run a new get query using the ObjectID you copied for the Jira published App.
https://graph.microsoft.com/beta/servicePrincipals/<your jira objectID>
If that worked, scroll down in the response preview result. We're going to patch a section of the code to include the roles.
Copy the entire block that starts with "appRoles" into your favorite text editor, like notepad++, for instance. Add the roles you want to it in notepad. In this case I'll add Jira-Users and Administrators. Here's my sample code. Use the GUID generator to generate random GUIDs to use.
"id": "GUID-Don't CHANGE - use the guid given",
"id": "GUID-Don't Change - use the guid given",
"description": "Administrators Only",
"id": "<Generate Random Guid and paste here>",
"description": "Jira Users",
"id": "<Generate Random Guid and paste here>",
Ok, note, AzureAD already includes a "user". However, it is set to pass a null value in the saml claim. So it's worthless.
Now, take your updated code block and paste it into the graph explorer - under request body (right below the get button).
Note - watch the brackets. Make sure you have them like I have them in the sample code. Remember to place a comma between roles. The last one does not have a comma. If you go back to add more roles, always add roles to the bottom, or you'll get errors.
Change get to Patch and click run query.
I change back to get and run a query again to verify the roles are added.
Great! you've updated the Graph. Give it a few minutes to reflect in AzureAD. You might need to click F5 to refresh the AzureAD page.
Now then, Let's go into the Jira Enterprise App in Azure AD and add the AD Groups and add the new roles to the app.
Open an icognito window with firefox, click the little yellow saml icon in the upper left to open the trace window and login to your jira instance with your AzureAD/Office365 credentials.
Check the SAML trace, you'll see the little bubble for saml, click it and click the saml tab. You'll see the claims. Make sure your groups are there.
Now the magic.
Go into the Resolution SAML Module and scroll down to groups. Create the custom mapping.
And there you go AD Groups in Jira (or Confluence or whatever). Test your login again and see if your groups passed correctly.
If you caught on, you're probably correct, I could have just called the role the exact Jira Security group name and skipped the mapping. That's all hindsight at this point, but a good recommendation for you to think about.
Gregory Van Den HamCommunity Leader
Teams break work down in order to help simplify complex tasks. This is often done iteratively, with tasks being broken down into smaller tasks and so on until the work is accurately captured in well-...
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