Improve error handling for invalid tokens during login #2575
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR enhances the error handling during the login process to provide users with more informative error messages when they attempt to log in with an invalid token. This addresses issue #2565 .
Key Changes:
Modified
get_token_permission
:get_token_permission
function now directly raises aValueError
if there is anHTTPError
during thewhoami
call. This allows the original error message from the server to be included, giving users more context about the problem(e.g., "Invalid or expired token")
.LocalTokenNotFoundError
is no longer explicitly caught, as it's essentially an invalid token scenario, and theHTTPError
fromwhoami
will handle it.Updated
_login.py
:_login
function continues to useget_token_permission
to check token validity.get_token_permission
raises aValueError
, the error is sent to the user, providing them with the more informative server error message.