-
Notifications
You must be signed in to change notification settings - Fork 0
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
OIDC is broken with requests-auth 8.0.0 #639
Comments
The first fix is trivial, we can just wrap this in a try/except and everything works. However, the second one is more problematic. We could of course just use the private attribute, and I see we're using the private I'm guessing we're using these private methods/attributes because we're trying to do something the package doesn't do, from context it seems like we want to force a refresh, but requests-auth doesn't support this. @da1910 do you remember why we have this in here? Is it worth trying to contribute this upstream? |
For reference, Colin-b/requests_auth#81 is the PR that introduced this change |
The issue, as I recall, was if you provide a refresh token to the builder you can get into a situation where the initial request to get an access token also triggers the refresh token to be rotated. I don't think this was properly handled in requests-auth, and we ended up with an out of date refresh token. It might be worth seeing if it's still and issue and if so contributing a fix. This was an expedient fix at the time. |
In that case, I'll create a separate issue to improve fundamentally how we do creating a session with a refresh token, which will probably involve seeing if we can contribute an improvement to requests_auth. This ticket will address the immediate failure with requests_auth 8.0.0 |
OIDC is broken in two different ways when using requests-auth 8.0.0:
OAuth2
class has changed fromrequests_auth.authentication
torequests_auth
TokenMemoryCache.forbid_concurrent_missing_token_function_call
is now a private attributeThe lock file currently pins the package at a version <8, presumably because this version increase broke the tests.
The text was updated successfully, but these errors were encountered: