You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature request to add new method verify_sync or verify_blocking to AccessTokenVerifier and IDTokenVerifier that will have the same behavior as verify but not be async. I see the README has some instructions on how to make sync calls but does not address how to get the JWK synchronously.
We are an Okta customer with a synchronous Python application written in Django. The async implementation for AccessTokenVerifier.verify and IDTokenVerifier.verify is causing issues for us. Our application is not written with coroutines and due to other implementation issues, we don't want to use run_until_complete. We can't rewrite our entire application to be async at this time.
This change would involve a lot of duplicated code to make async methods sync / blocking, but it would allow support for Python code that doesn't use coroutines.
The text was updated successfully, but these errors were encountered:
Feature request to add new method
verify_sync
orverify_blocking
toAccessTokenVerifier
andIDTokenVerifier
that will have the same behavior asverify
but not be async. I see the README has some instructions on how to make sync calls but does not address how to get the JWK synchronously.We are an Okta customer with a synchronous Python application written in Django. The async implementation for
AccessTokenVerifier.verify
andIDTokenVerifier.verify
is causing issues for us. Our application is not written with coroutines and due to other implementation issues, we don't want to userun_until_complete
. We can't rewrite our entire application to be async at this time.This change would involve a lot of duplicated code to make async methods sync / blocking, but it would allow support for Python code that doesn't use coroutines.
The text was updated successfully, but these errors were encountered: