-
Notifications
You must be signed in to change notification settings - Fork 10
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
Access token length check is too strict #4
Comments
Fixes and improvements to the validation of authorization codes and access tokens, resolves issue #4.
@Shub77 I have made a fix to this. Let me know if this is resolved for you or if you are still experiencing issues. |
Now a warning is issued. This happens because the |
I think the solution is to remove validation of the access token. If the token is invalid the graph api will return an error to a request. I will include this change in the next release, but you should still be able to use the current release given it only issues a warning. |
Yes, thank you. |
Latest commit has removed the access token validation. |
In
_create_headers(self)
method inOneDrive
class there is a check which requires the Access Token length to be >=1800 bytes.The Access Tokens retrieved from my response urls are shorter, ~1024 bytes, but are valid ones. I modified the raise call so that it reports the lenght of the Access Token, see last line of traceback: 1164 bytes.
Fixing the size check, I found out the token is valid and works, even if it is shorter than 1800 bytes.
The text was updated successfully, but these errors were encountered: