Skip to content
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

Back-channel Single Sign Out Support #177

Open
kreintjes opened this issue Mar 14, 2024 · 0 comments
Open

Back-channel Single Sign Out Support #177

kreintjes opened this issue Mar 14, 2024 · 0 comments

Comments

@kreintjes
Copy link

Hi, first of all thanks for the gem! I was wondering if the gem also supports the OpenID Connect back-channel sign out protocol: https://openid.net/specs/openid-connect-backchannel-1_0.html. I could implement this myself by building some controller action for it, but then I would need to perform lots of validations on the jwt_token. I believe many of these validations are already implemented in this gem, so it would be nice if it is possible to reuse that. Is this something that is supported now or can this be achieved somehow?

Since this gem is basically a Rack Middleware (if I understand correctly), I think it would be difficult to access the code of this gem (and the config for the OP defined in the strategy) from a custom controller. Is that correct?

If so, would it be possible to implement the back-channel sign out endpoint in this gem, which when called with a valid token will then execute some block defined in the strategy configuration. That way you would only need to configure the actions to be taken when single sign out is called successfully and all the (JWT) validations can be handled by the gem. Would something like that be possible?

@kreintjes kreintjes changed the title OpenID Connect back-channel Single Sign Out Support Back-channel Single Sign Out Support Mar 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant