AAD Claims UPN vs On-Premise AD UPN


AAD Claims UPN vs On-Premise AD UPN



I thought UserPrincipalName (UPN) are single valued per user in the Directory, but when I run an LDAP query for a specific user, I get the UPN: AO0S0020@mydomain.local,


UserPrincipalName


AO0S0020@mydomain.local



And when running an OAuth (OpenId Connect) authorization against Azure AD (which is synced using AD Connect), I see that the claims UPN for the same user: nati@mydomain.com


AD Connect


nati@mydomain.com



What am I missing here?



The question is widely applicable to a large audience. A detailed canonical answer is required to address all the concerns.



The architecture that allows such difference.




1 Answer
1



You are missing the concept of Alternate login id.



It seems your Azure AD connect is configured with alternate login id. Thus the difference.





I tried to fetch the AlternateLoginID attribute from the LDAP, but it does now exist.
– Nati
Jul 2 at 13:28



AlternateLoginID





AlternateLoginID is configured in ADFS and ADConnect, not in AD. Usually, it points to the email AD property.
– andresm53
Jul 5 at 17:49





I would get the guid (or OID) from AD for nati@mydomain.com and then look for this oid guid value in another field in LDAP.
– Sql Surfer
yesterday






@SqlSurfer the OID in Azure AD is completely disconnected from your on-premises world. So there is nothing to match with it. The link from cloud to on-prem is source anchor. And its configuration varies and can be changed (Azure AD Connect settings).
– astaykov
15 hours ago






By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Popular posts from this blog

JMeter fails on beanshell imports

Why in node-red my HTTP POST no receive payload from inject?

PHP contact form sending but not receiving emails