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

More clearly differentiate authentication error from authorization error in text #1832

Closed
JeroenvdV opened this issue Jun 11, 2024 · 1 comment

Comments

@JeroenvdV
Copy link

What would you like?

When clicking a deep link while not signed in, the page may indicate an authorization problem such as:

"YOU ARE NOT ALLOWED TO VIEW MEETINGS."

Below that is stated in small text:

"You might be able to view this page by logging in"

I think the messages would be better reworded in such a way that the lack of authentication is shown first, as most likely anything that requires authorization first requires being authenticated.

Why is this needed?

The way this error is currently presented may falsely imply that the user is already authenticated, but not authorized, which is confusing.

Other information

No response

@tomudding
Copy link
Member

This is planned for/part of GH-1798 and will include the differentiation between 401 (not authenticated) and 403 (not authorized).

@tomudding tomudding closed this as not planned Won't fix, can't repro, duplicate, stale Jun 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants