-
Notifications
You must be signed in to change notification settings - Fork 1.3k
clean up tokens on deauthorize #3872
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
Conversation
Thanks Alex!
This is where I end up at (correct-looking EDIT: Actually, why even attempt to redirect to |
@jankeromnes, thanks for testing! First of, it tries to redirect is an error page (and not to login) and that's what's expected. An error page that is only rendered if logged in is problematic at least. :-( In this particular case though the flow and the resulting redirect is happening in a separate browser tab, so the target for redirect should not be the sorry page. Indeed it should redirect to /login-error (symmetrical to /login-success) and propagate to the still open login page, which will close the extra tab and, that's the plan, render a message. One step at a time. |
d570879
to
7218c2a
Compare
@jankeromnes, I extracted #3915 from here. I turns out there is a tail to that problem. |
/werft run 👍 started the job as gitpod-build-at-bugfixes.3 |
@csweichel, could you have a look at the changes left in this PR, please? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change LGTM
clean up tokens on deauthorize
fixes #3800
how to test
temporarily disable terms acceptance check in API