Skip to content

Commit 72f951d

Browse files
committed
Fix images path
1 parent 8f10164 commit 72f951d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

authentication/AzureAD/README.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -54,11 +54,11 @@ The Authorization Code flow is best used by server-side apps in which the source
5454

5555
The Client Credentials flow is intended for server-side (AKA "confidential") client applications with no end user, which normally describes machine-to-machine communication. The application must be server-side because it must be trusted with the client secret, and since the credentials are hard-coded, it cannot be used by an actual end user. It involves a single, authenticated request to the token endpoint which returns an access token.
5656

57-
![Microsoft Entra ID Client Credential Flow](/images/AzureAD/ClientCredential.png) (© Microsoft)
57+
![Microsoft Entra ID Client Credential Flow](images/ClientCredential.png) (© Microsoft)
5858

5959
The Microsoft identity platform supports the OAuth 2.0 Resource Owner Password Credentials (ROPC) grant, which allows an application to sign in the user by directly handling their password. Microsoft recommends you do not use the ROPC flow. In most scenarios, more secure alternatives are available and recommended. This flow requires a very high degree of trust in the application, and carries risks which are not present in other flows. You should only use this flow when other more secure flows cannot be used.
6060

61-
![Microsoft Entra ID Password Flow](/images/AzureAD/PasswordFlow.png) (© Microsoft)
61+
![Microsoft Entra ID Password Flow](images/PasswordFlow.png) (© Microsoft)
6262

6363
## Prerequisites
6464

@@ -161,4 +161,4 @@ If you are unsure about which option to choose, take the time to read [this arti
161161
# License
162162

163163
[Apache 2.0](/LICENSE)
164-
164+

0 commit comments

Comments
 (0)