Skip to content

Optimize the registration of OIDC BackChannel logout routes  #43046

Closed

Description

Description

Currently, OIDC BackChannelLogoutHandler is a CDI bean which @Observes the Router and iterates over all static tenants and registers tenant specific routes for managing back-channel logout callbacks if required.

It should be recorded instead in OidcRecorder, similar to have it is done in the WebAuthn extension, though I believe we should not deal with prefixes in case of the main router.

Implementation ideas

BackChannelLogoutHandler#setup and BackChannelLogoutHandler#addRoute should be gone and re-implemented in the OIdcRecorder. OidcRecorder iterates over the default and all other static tenants, so hopefully, all what will be needed, is to check if the current static tenant requires a back-channel logout support and if yes, router.post should be done adding BackChannelLogoutHandler.

OidcBuildStep should use a built item representing the main Router to pass RuntimeValue<Router> to OidcRecorder. I'm assuming it is VertxWebRouterBuildItem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions