Skip to content
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Go to file
Cannot retrieve contributors at this time
title date draft summary description tags images editLink
Set a Custom Name Claim Type in Azure AD Secured Web API
2021-04-06 22:16:29 +0300
Overriding the default name claim type configuration in Microsoft Identity.
Overriding the default name claim type configuration in Microsoft Identity.

In this article, we'll learn how to set a custom name claim type to our ClaimsPrincipal's primary identity in ASP.NET Core Web API. Our API uses Azure AD as its identity provider. That will make it possible for us to retrieve the request initiator's name in our controllers' action methods by simply calling


which will return the value of the claim we specified.

The Defaults

In a standard authentication flow, the user signs in to the client app (1) through Azure AD and obtains an access token as a JWT (2). This token is then used as a bearer token to authenticate the user when calling the Web API (3).

Authentication Flow


To authenticate the user, the respective handler decodes, verifies the access token, and extracts the claims its payload. When ASP.NET instantiates the ClaimsPrincipal object for our request, it uses those claims to establish its identity. We enable the Azure AD authentication into our HTTP request/response pipeline, by simply adding


to the application startup. "AzureAd" is the name of the respective section in our app settings. For this example, we'll use the "preferred_username" claim which is included in the access token's payload issued by Azure AD. We can retrieve its value by calling


This will search the User.Claims collection for a claim with the provided type and return it if one is found.

Our ClaimsPrincipal's primary identity has a Name property. It would make sense to get the value of the "preferred_username" claim when we call


but instead, we get null, even though the authentication is successful and the "preferred_username" claim is available.

Null Identity Name

The reason is that the default name claim type is set to something different and since User.Claims don't contain it, we end up with null.

Find Default Name Claim

The Solution

We set the default name claim type by using a different overload of the AddMicrosoftIdentityWebApi method:

    .AddMicrosoftIdentityWebApi(options =>
        Configuration.Bind("AzureAd", options);
        options.TokenValidationParameters.NameClaimType = "preferred_username";
    options => Configuration.Bind("AzureAd", options));

Now we can easily retrieve the name of our user who initiated the request:

Populated Identity Name


The "preferred_username" claim's value is mutable and might change over time, hence, it should not be used as a primary key or for authorization decisions. There are immutable claims for such tasks. Refer to the docs for more details.