-
Notifications
You must be signed in to change notification settings - Fork 16
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
docs: recommend using the route logout #120
Comments
I don't know where to document this. We don't actually recommend using the authenticate sign_out endpoint anywhere. |
Let's add some text to the single sign out docs page. I think what's missing is:
|
@XxEnigmaticxX ket's keep an eye on this. Currently I just redirect people to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There was a bug causing logout on the authenticate service to work differently from logout on the proxy service. (they were actually using different sessions) The above PR should fix that problem.
However using logout from authenticate is not ideal. It can't delete the cookie on the route itself, and we utilize a caching layer for session access, so it may take a few seconds for the user to appear logged out on the route. We should update the documentation to recommend using the route logout.
Originally posted by @calebdoxsey in pomerium/pomerium#3592 (comment)
The text was updated successfully, but these errors were encountered: