-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Hooks around AuthorizationController / Single Sign Out feature #1062
Comments
How about to use before_successful_response and after_successful_response hooks?
|
@nbulaj thank you for the response! Unfortunately, it seems |
Maybe you can make some research if we can add a context to existing hooks in order to provide required binding? If it is hard to implement, you can send a PR with before and after hooks for authorization 👍 |
Merged, thanks! |
Hey there! I'm working on the Single Sign Out feature in my project, which actually means:
There's an example of how Google does that - http://romain.pechayre.me/blog/2015/06/26/single-sign-out-problem/ - and I've tried to implement it in the same way.
The idea I've ended up with is to store in the main auth cookies a list of service applications, that have requested the auth. And upon logout, on the side of the every service application there should be a redirection to
auth-provider.com/logout
which redirects user back to every logged in service and forces him to log out.The code is pretty simple, but it requires monkey-patching Doorkeeper, which isn't very good idea considering I had to copy-paste parts of existing code that might change in the future:
And then in some SessionsController:
This seems to work (besides possible too many redirections error), but since I had to monkey-patch Doorkeeper I have the following questions:
Is there a chance to add some hooks to
AuthorizationsController
?So on the client side it might be something like:
Maybe that feature (Single Sign Out) could be interesting to the users?
In case I could propose a PR to add that opt'able feature to the gem.
The text was updated successfully, but these errors were encountered: