Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
  • Loading branch information
@deepu105
deepu105 authored Apr 19, 2024
1 parent 504c940 commit 0049322
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions _source/_posts/2024-02-27-spring-security-pkce.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -29,9 +29,9 @@ OAuth 2.0 and OpenID Connect are the authentication and authorization _de facto_

The OpenID Connect core specification defines the following roles:

1. End-User: Human participant
2. Authorization Server: The server issues access tokens to the client after successfully authenticating the resource owner and obtaining authorization.
3. Client: An application making protected resource requests on behalf of the resource owner (the end-user) and with its authorization.
1. **End-User**: Human participant
2. **Authorization Server**: The server issues access tokens to the client after successfully authenticating the resource owner and obtaining authorization.
3. **Client**: An application making protected resource requests on behalf of the resource owner (the end-user) and with its authorization.

From the OpenID Connect specification, the authentication using Authorization Code Flow has the following steps:

Expand Down

0 comments on commit 0049322

Please sign in to comment.