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
The docs also suggest in several places that in some circumstances key should be a cryptography.hazmat.primitives.asymmetric.rsa.RSAPrivateKey, so seems like this type annotation could use work in that regard as well.
oops, what I mentioned is all brought up in this issue: #848
In various APIs, most notably "api_jwt.encode" and "api_jwt.decode", key is passed in and annotated to be of type "str" (example).
However, this does not allow all keys to be used.
For example, using a token generated with https://token.dev/ the following works with a key of types bytes, but not str:
This works as expected, but there is no string which can be used here as the key.
The text was updated successfully, but these errors were encountered: