This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(176, 7.000000000000001%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EE%3C/text%3E%3C/svg%3E)
Hi everyone
I have a question...
Is “upn” claim with ADFS the same as “name” claim with Azure (the values are the same on my app) ¿?
Hello @Edeejay ,
Just checking in to see if the below answer helped. If this answers your query, please don’t forget to click "Accept the answer" and Up-Vote for the same, which might be beneficial to other community members reading this thread. And, if you have any further query do let us know.
Thanks,
Hello @Edeejay ,
Thanks for reaching out.
Yes, name claim( http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name ) mapped with user.userprincipalname source attribute as additional claims for enterprise application. This is default claims which can be verified from User attributes & claims setting as shown below and this can be modified as required by adding new claim and deleting default one.
Hope this helps.
------
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.
@sikumars-msft Thanks for your reply.
I want to make this change only for an app, Is this posible? It´s like you are explain?
Thanksss
Cloud you please help me understanding in detail? are you expecting to get upn claim directly instead through name claim for particular app that you integrated with AAD in Enterprise Application? if so then create new claim as shown below:
@sikumars-msft
Yes It´s only for one app in particular that we want to login via oAuth2.
Now, This app is logging throw ADFS using UPN.
Above steps mentioned previous were for SAML authentication, in case of Oauth authentication (JWT based Access_token) then UPN (UserPrincipalName) claim is automatically included see below jwt token for your reference, you can manage these claims from Token Configuration blade from azure AD, to learn more refer how to configure optional claim to your application. Hope this helps
**JWT Access_token: **
**Add optional claim: **
------
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.
@sikumars-msft
I´m configuring that from "app registration..."
I´ll send your comments to my partners...
UPN claim, on Oauth Authentication, is automatically included.
I don´t have to configure anything on this registered app.
Sorry ...
Certainly, and let me know how that goes also please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.
@Edeejay ,
I just wanted to check in and see if you had any other questions or if you were able to resolve this issue? If you have any other questions, please let me know.
Thank you for your time and patience throughout this issue.
------------
Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.