You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A Web API is secured by [validating the token](https://docs.microsoft.com/en-us/azure/active-directory/develop/access-tokens#validating-tokens) they receive from callers. When a developer generates a skeleton Web API code using [Visual Studio](https://aka.ms/vsdownload), token validation libraries and code to carry out basic token validation is automatically generated in the project. An example of the generated code using the [asp.net security middleware](https://github.com/aspnet/Security) and [Microsoft Identity Model Extension for .NET](https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet) to validate tokens is provided below.
16
+
A Web API that accepts bearer token is secured by [validating the token](https://docs.microsoft.com/en-us/azure/active-directory/develop/access-tokens#validating-tokens) they receive from callers. When a developer generates a skeleton Web API code using [Visual Studio](https://aka.ms/vsdownload), token validation libraries and code to carry out basic token validation is automatically generated in the project. An example of the generated code using the [asp.net security middleware](https://github.com/aspnet/Security) and [Microsoft Identity Model Extension for .NET](https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet) to validate tokens is provided below.
17
17
18
18
```CSharp
19
19
public void ConfigureAuth(IAppBuilder app)
@@ -29,7 +29,7 @@ A Web API is secured by [validating the token](https://docs.microsoft.com/en-us/
29
29
}
30
30
```
31
31
32
-
The code above will validate the issuer, audience, and the signing tokens, but often the developer's requirements are more than what the defaults provide. Examples of these requirements can be:
32
+
The code above will validate the issuer, audience, and the signing tokens, which is usually sufficient for most scenarios. But often the developer's requirements are more than what the defaults provide. Examples of these requirements can be:
33
33
34
34
- Restricting the Web API to one or more Apps (App IDs)
35
35
- Restricting the Web API to just one or more tenants (Issuers)
@@ -322,7 +322,7 @@ If you are using this sample with an Azure AD B2C custom policy, you might want
322
322
323
323
Use [Stack Overflow](http://stackoverflow.com/questions/tagged/msal) togetsupportfromthecommunity.
0 commit comments