Support OIDC extended claims #1785
Merged
Conversation
This file contains hidden or 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
|
Going to let the pull hang for a while and make nice with Travis. |
# Conflicts: # cas-server-webapp/build.gradle
# Conflicts: # cas-server-support-cookie/src/main/java/org/apereo/cas/web/support/CookieRetrievingCookieGenerator.java
# Conflicts: # cas-server-support-cookie/src/main/java/org/apereo/cas/web/support/CookieRetrievingCookieGenerator.java
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #1773
What
This patch adds support for the following OIDC claims:
The "confirm" view is also revamped to match the new CAS thymeleaf look and feel.
In conjunction with adding support for max_age, fixed a bug related to tracking the authentication date in particular when CAS attempts to reuse the same TGT.
amr/acr claims are yet to be supported.
No change to the docs needed. All behavior is controlled and configured internally.
How
Briefly, the OIDC module takes advantage of conditional bean configuration to build on top of the OAuth module. The beans override and inject themselves into the context where and when necessary to handle consent, and managing callback urls.