Describe the bug
When a user tries to sign up/login using GitHub OAuth and clicks "Cancel" instead of "Authorize",
the application returns a raw error response:
"No user information from OAuth provider" with status 401 Unauthorized.
This is not user-friendly and misleading, as the user intentionally cancelled the login process.
Steps To Reproduce
- Go to the signup/login page
- Click on "Sign in with GitHub"
- On the GitHub authorization screen, click "Cancel"
- Observe the error response shown on the screen
Expected behavior
When the user cancels the OAuth flow, the application should detect the
error=access_denied parameter and display a user-friendly message such as:
"Login cancelled by user" or "Authorization was denied"
Instead of showing a 401 Unauthorized error.
Packages
(Not sure / can be filled by running npm run refine whoami if required)
Additional Context
The backend seems to assume that OAuth always succeeds and does not handle
the cancellation (error=access_denied) case properly.
Handling this case will improve user experience and prevent confusing error messages.
Describe the bug
When a user tries to sign up/login using GitHub OAuth and clicks "Cancel" instead of "Authorize",
the application returns a raw error response:
"No user information from OAuth provider" with status 401 Unauthorized.
This is not user-friendly and misleading, as the user intentionally cancelled the login process.
Steps To Reproduce
Expected behavior
When the user cancels the OAuth flow, the application should detect the
error=access_deniedparameter and display a user-friendly message such as:"Login cancelled by user" or "Authorization was denied"
Instead of showing a 401 Unauthorized error.
Packages
(Not sure / can be filled by running
npm run refine whoamiif required)Additional Context
The backend seems to assume that OAuth always succeeds and does not handle
the cancellation (
error=access_denied) case properly.Handling this case will improve user experience and prevent confusing error messages.