I have tried all the usual things -- using upn for both fields, exposing upn in azure as an optional claim.
using preferred_username in Azure - trying email in all sorts of configurations. The problem i was getting was when i set the directory id to our upn it was giving me a weird directory id as shown in the original post in this thread. now i am getting it to show my email address which is not even in ifs. so i am unclear on which way the mapping goes and to what fields. Thanks
this by far is the most help I’ve gotten so far. I have seen the video although we had to use version 2 not 1 the problem that we have is when we use upn for our Azure claim we get an internal server error.
Use the correct active directory attribute that you use for Directory ID (Username) for Claim.
even if i remove the url per ---Please remove the User Infor endpoint from the IDP Configurations in order to work with Arritue Mappers.
we still get internal server error.
for our directory id i have tried all combinations of username and even email address.
any thought on what the internal server error is or how i can find out?
Hi, Just to update on my previous reply. We have SSO working now. Above the standard setup shown in the YouTube Video we had to ... Add 2 Optional Claims in the Azure App Registration: upn with Token Type ID upn with Token Type Access
In IFS add an IdP Attribute Mapper Name= upn Claim = upn
Then obviously set the Directory ID of the user to be the Azure upn.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.