Assert on token format caused by inconsistency with authlib #140
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.
The library has a check
can_refresh_access_token
inside which
isinstance(self.scope, (list, tuple))
is checkedOtherwise the access token is not refreshed and fails with an error
It would be better if an error occurred when trying to initialize the library with a scope as a string, or perform an automatic split occurred.
I'm not sure which strategy others will consider better.
For context, I was run into a scope parameter inconsistency issue with the authlib library
I first authorize the user like this
and in the saved token the scope has the type string with spaces.
Then I worked with the API and did not understand why the token could not be updated.
The solution to the problem is to transform the token when saving it for the first time on the application side.