We are switching from ADFS to Azure for authentication. We're having issues with Azure. One thing we noticed with ADFS authentication when we run the microsoft claims xray we have several claims that are returned that are not available when we run the same microsoft claims xray using Azure authentication. What claims are needed for Azure and/or what is Infor ION looking for?
Running microsoft claims xray using ADFS authentication we get:
groupsid, name, primarygroupsid, primarysid, upn, userip, windowsaccoutname --There are a few others, but I figured these were the key ones.
When we run the microsoft claims xray using Azure authentication we get:
upn and that's about it.
I tried having our microsoft engineers set the AcceptMappedClaims property to true in our app manifest so the following claims would be allowed which I thought would allows the claims to show up that were missing but I still get the same xray results without these claims:
http://schemas.microsoft.com/ws/2008/06/identity/claims/windowsaccountname
http://schemas.microsoft.com/ws/2008/06/identity/claims/primarysid
http://schemas.microsoft.com/ws/2008/06/identity/claims/primarygroupsid
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/sid
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/x500distinguishedname
Can anyone confirm the claims needed and any potential Azure properties needed to allow them to pass?
