Skip to content

Commit 221e64f

Browse files
committed
improve pkce diagram
1 parent c5f2109 commit 221e64f

File tree

2 files changed

+1
-1
lines changed

2 files changed

+1
-1
lines changed
Loading

_source/_posts/2024-02-27-spring-security-pkce.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ As browser and mobile applications _cannot_ hold credentials securely and theref
6060

6161
The modified flow has the following steps:
6262

63-
{% img blog/spring-security-pkce/auth0-authorization-code-pkce.png alt:"Authorization Code Grant" width:"800" %}{: .center-image }
63+
{% img blog/spring-security-pkce/auth0-authorization-code-pkce.png alt:"Authorization Code Grant" width:"850" %}{: .center-image }
6464

6565
1. The Client creates and records a secret named the "code_verifier" and derives a transformed version referred to as the "code_challenge", which is sent in the OAuth 2.0 Authorization Request along with the transformation method.
6666
2. The Authorization Endpoint responds as usual but records the "code_challenge" and the transformation method.

0 commit comments

Comments
 (0)