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

403s from the API should log out user #15312

Closed
Palakp41 opened this issue Oct 2, 2019 · 1 comment · Fixed by #15426
Closed

403s from the API should log out user #15312

Palakp41 opened this issue Oct 2, 2019 · 1 comment · Fixed by #15426
Assignees
Labels

Comments

@Palakp41
Copy link
Contributor

Palakp41 commented Oct 2, 2019

As a user who is cancelled, anytime the api endpoint comes back with 403 error, the user should be logged out automatically.

We return a 401 for when a user is not authorized to access a resources and 403 when they are disabled. So we should log them out on 403 and not on 401.

@Palakp41 Palakp41 added this to the Sprint 8 - Heliotrope milestone Oct 2, 2019
@hoorayimhelping hoorayimhelping self-assigned this Oct 8, 2019
@hoorayimhelping hoorayimhelping changed the title Log user out from chronograf when user is cancelled 403s from the API should log out user Oct 9, 2019
@hoorayimhelping
Copy link
Contributor

Confirmation from Brandon: All 403s from the API should log the user out of the UI. 401s can be sent for specific resources, but a 403 will always mean forbidden. This applies to all endpoints, even /me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants