Closed tl24 closed 2 years ago
@tl24 Thanks for posting this issue. I'll take a look. But first, I'd like to clarify few things regarding your code:
1) entrypoint is decode_token
func, right?
2) why do you cache verifier if it should cache jwks by itself https://github.com/okta/okta-jwt-verifier-python/blob/master/okta_jwt_verifier/jwt_verifier.py#L24 ?
@tl24 Yes, you're right, timeout value is not being passed. As a temporary workaround I can suggest use custom RequestExecutor, where you can pass timeout via fire_request
method. Meanwhile, I'll fix this issue.
Yes, thanks. Fix is ready and currently pending review. I'll post here when we release new version.
@tl24 jwt-verifier v0.2.1 has been released. I'm closing this issue as resolved. Feel free to reopen this issue or create a new one if your problem exists still
We are having an issue that seems to be on first call to verify when it tries to retrieve the JWK. It looks like a timeout value is not being passed to acachecontrol somewhere. But I guess it still gets cached as subsequent calls succeed.
I get this issue calling AcessTokenVerifier.verify with an auth token from a custom okta auth server.
I'm using okta-jwt-verifier 0.2.0 Calling code: