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

Token invalid | 401 Unauthorized error when loading the page #424

Closed
mario-nt opened this issue Jan 3, 2024 · 3 comments
Closed

Token invalid | 401 Unauthorized error when loading the page #424

mario-nt opened this issue Jan 3, 2024 · 3 comments
Assignees
Labels
Bug Incorrect Behavior
Milestone

Comments

@mario-nt
Copy link
Contributor

mario-nt commented Jan 3, 2024

A 401 Unauthorized error is shown when opening the index GUI with Firefox:
image
Detail:
image

@mario-nt mario-nt added the Bug Incorrect Behavior label Jan 3, 2024
@cgbosse cgbosse moved this to BUG in Torrust Solution Jan 8, 2024
@cgbosse
Copy link
Member

cgbosse commented Jan 16, 2024

@mario-nt any progress on this?
What is your priority with this issue?

@cgbosse cgbosse added this to the v3.0.0 milestone Jan 16, 2024
@mario-nt
Copy link
Contributor Author

@cgbosse I haven't started working on it yet, I'm planning of finishing the light/dark mode PR and then continue with the rest of the issues/PRs I have assigned. I would start prioritizing the issues that will be part of the V3.0 release and critical bugs and errors from now on.

@josecelano
Copy link
Member

This is a problem described here.

My first thought was we should discard the token in this case (if the user was removed). But we do not know if the user was removed or does not have permission to see that resource anymore.

Maybe we have to keep the frontend as it is. The users should receive a notification that their accounts were removed. So they must know why they do not have access anymore to a resource.

Alternatively, we could check that the account still exists. but I do not think that's a good idea. Accounts should not be removed like that.

I'm going to close the issue. Feel free to open it again if you think I'm wrong or there is a better approach to this.

cc @WarmBeer @da2ce7

@github-project-automation github-project-automation bot moved this from BUG & Security to Done in Torrust Solution Jan 25, 2024
@mario-nt mario-nt assigned josecelano and unassigned mario-nt May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Incorrect Behavior
Projects
Status: Done
Development

No branches or pull requests

3 participants