-
Notifications
You must be signed in to change notification settings - Fork 580
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Support for OIDC logout when using cookies. * Refactored OidcConfig as it was too big. * Only require encryption for the id token when it is expected to be used. Signed-off-by: Tomas Langer <tomas.langer@oracle.com>
- Loading branch information
1 parent
f34ada8
commit 40934aa
Showing
32 changed files
with
3,502 additions
and
361 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
OIDC | ||
---- | ||
|
||
New Open ID Connect features in Helidon. | ||
|
||
# OIDC Logout | ||
The capability to logout requires two pieces of information: | ||
1. The token (JWT) that we usually have in a cookie or in a header | ||
2. The ID token, that we get when obtaining JWT using the code flow | ||
|
||
As we need both, we need to store both of these tokens in a cookie (or get them from a header). | ||
This also requires encrypting these tokens, as the ID token is not public information. | ||
|
||
To achieve this, we need | ||
|
||
1. either configuration of encryption as part of OIDC configuration, | ||
or use `Security` instance registered in global context (and named encryption/decryption configured). | ||
2. support for encrypted JWT and capability to encrypt existing JWT ourselves | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.