-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenID logout / more extensibible OpenIdConfiguration #8216
Comments
…nsible Signed-off-by: Lachlan Roberts <[email protected]>
@keller-j I have a PR to make Not sure how we would implement the logout, but I will take a closer look tomorrow. Feel free to open a PR yourself if you have an idea of how to do this. |
Signed-off-by: Johannes Keller <[email protected]>
@lachlan-roberts thanks a lot for the support. This fitted exactly my needs. That way I could easily also process the I included my current implementation for Note this isn't the perfect solution for the logout problem. Also I'm not quite sure whether it's OK to return Feel free to re-use / and change the proposed snippet for logout. NOTE: didn't test the new implementation in production, but a similar implementation in my project where I'm extending |
Signed-off-by: Lachlan Roberts <[email protected]>
Signed-off-by: Lachlan Roberts <[email protected]>
Signed-off-by: Lachlan Roberts <[email protected]>
Issue #8216 - make processing of metadata in OpenIdConfiguration extensible
@lachlan-roberts did you have the chance to think about OpenIdAuthenticator logout? |
…endpoint redirect Signed-off-by: Lachlan Roberts <[email protected]>
Signed-off-by: Lachlan Roberts <[email protected]>
@lachlan-roberts looks really good to me! Thanks a lot for the support. Found a minor issue in one of the constructors, left a comment at the pull-request. |
Signed-off-by: Lachlan Roberts <[email protected]>
Signed-off-by: Lachlan Roberts <[email protected]>
Issue #8216 - OpenID Connect RP-Initiated Logout
Thanks a lot! |
Target Jetty version(s)
10.0.x
11.0.x
12.0.x
Additional Details
I'm currently working with
jetty-11
and availableOpenIdAuthenticator
. My OpenID (SSO) server is running onkeycloak-18
while trying to logout via client application (jetty) I realized that this isn't working at the moment. While having a look atOpenIdConfiguraion
I realized that no information aboutend_session_endpoint
isn't even processed inOpenIdConfiguration
:https://github.com/eclipse/jetty.project/blob/5fe999caa25755dec57d21bc3d694f67de4e45ab/jetty-openid/src/main/java/org/eclipse/jetty/security/openid/OpenIdConfiguration.java#L119-#L130
At the moment I'm
extending OpenIdConfiguration
and loadingend_session_endpoint
information with a separate call similar to https://github.com/eclipse/jetty.project/blob/5fe999caa25755dec57d21bc3d694f67de4e45ab/jetty-openid/src/main/java/org/eclipse/jetty/security/openid/OpenIdConfiguration.java#L141-#L172 . Then in an extendedOpenIdAuthenticator
I'm reacting to a certain logout page with redirecting user toend_session_endpoint
or (depending on class configuration) also providingid_token_hint
(e.g., available viaHttpSession
) andpost_logout_redirect_uri
as stated in OpenID documentation: https://openid.net/specs/openid-connect-rpinitiated-1_0.html#RPLogoutEnhancement Description
OpenIdConfiguration
would be great if results fetched from OpenID configuration endpoint could be further processed for own needs by simply extendingOpenIdConfiguration
and implementing / overriding protected method, e.g.,processMetadata(Map<?, ?> fetchedMetadata)
which can be called indoStart
with information ofdiscoveryDocument
:https://github.com/eclipse/jetty.project/blob/5fe999caa25755dec57d21bc3d694f67de4e45ab/jetty-openid/src/main/java/org/eclipse/jetty/security/openid/OpenIdConfiguration.java#L119 . Since there are lot of configuration settings not yet considered for current implementation possibility to simply process and store them along the configuration could come in handy.
OpenIdAuthenticator
could also support logout from SSO. Therefore additional information must be processed inOpenIdConfiguration
and considered inOpenIdAuthenticator
.The text was updated successfully, but these errors were encountered: