Hello,
we have followed this article to configure SSO between JIRA data-center and Azure Active Directory (AD). In a nutshell, the process involves creating an Enterprise Application and using the default SSO capabilities of AD to configure JIRA.
Users can authenticate against AD and are then logged into JIRA.
The problem is that users need to supply the AD internal email to log into AD, whereas we would like them to use their actual email to sign in. The AD internal email takes the form f42f08g5-02f9-4f55-ba9a-4a67763d2dp1@mysubscription.onmicrosoft.com, whereas the actual email could be xzy@gmail.com or similar. The actual email is stored in the User Principal Name attribute. The Azure AD is a pure cloud installation, not synced with a on-premise AD.
We did find a description of how to setup custom policies in AD B2C to use SAML, but the process described appears very complicated for what looks to me like a standard use-case.
I am aware that this mostly a Azure AD issue. I hope that someone here has perhaps had the same issue and could point me to a solution.
Thank you
Timo
Hi there, and answering my own question.
We did get it to work by using custom policies in AD B2C .
Would still be interested if there is any other solution.
Cheers,
Timo
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.