Skip to content

Commit 6aaca5e

Browse files
committed
removed *
1 parent 14e3c17 commit 6aaca5e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/api-management/authentication-authorization-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ What happens when a client app calls an API with a request that is secured using
4848
* The *resource server* validates the access token. Validation is a complex process that includes a check that the *issuer* and *audience* claims contain expected values.
4949
* Based on token validation criteria, access to resources of the [backend] API is then granted.
5050

51-
Depending on the type of client app and scenarios, different *authentication flows* are needed to request and manage tokens. For example, the *authorization code flow and grant type are commonly used in apps that call web APIs. Learn more about [OAuth flows and application scenarios in Azure AD](../active-directory/develop/authentication-flows-app-scenarios.md).
51+
Depending on the type of client app and scenarios, different *authentication flows* are needed to request and manage tokens. For example, the authorization code flow and grant type are commonly used in apps that call web APIs. Learn more about [OAuth flows and application scenarios in Azure AD](../active-directory/develop/authentication-flows-app-scenarios.md).
5252

5353

5454
### OAuth 2.0 authorization scenarios

0 commit comments

Comments
 (0)