Skip to content

Commit

Permalink
Update docs/src/main/asciidoc/security-authentication-mechanisms-conc…
Browse files Browse the repository at this point in the history
…ept.adoc

Co-authored-by: Sergey Beryozkin <[email protected]>
  • Loading branch information
michelle-purcell and sberyozkin committed Jun 19, 2023
1 parent 478a708 commit b15b813
Showing 1 changed file with 1 addition and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -180,7 +180,7 @@ The Bearer authentication mechanism extracts the token from the HTTP Authorizati
The Authorization Code Flow mechanism redirects the user to an OIDC provider to authenticate the user's identity.
After the user is redirected back to Quarkus, the mechanism completes the authentication process by exchanging the provided code that was granted for the ID, access, and refresh tokens.

You can verify ID and access JSON Web Key (JWK) tokens by using the refreshable JWK set or introspect them remotely.
You can verify ID and access JSON Web Token (JWT) tokens by using the refreshable JSON Web Key (JWK) set or introspect them remotely.
However, opaque, also known as binary tokens, can only be introspected remotely.

[NOTE]
Expand Down

0 comments on commit b15b813

Please sign in to comment.