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
When decrypting or verifying a token, it might be useful to dedicate specific exception for malformed input (ex not a jwt) vs an invalid token (non verified signature, expired token, exc). This is both at the code level AND in the docstring methods.
This is not a strong requirement, but would be eventually nice to have so that HTTP Handlers using the token verifier / token decrypter can yield meaningful and informative error messages (with the proper concern for minimal information disclosure), which is currently somewhat hard to do.
The text was updated successfully, but these errors were encountered:
When decrypting or verifying a token, it might be useful to dedicate specific exception for malformed input (ex not a jwt) vs an invalid token (non verified signature, expired token, exc). This is both at the code level AND in the docstring methods.
This is not a strong requirement, but would be eventually nice to have so that HTTP Handlers using the token verifier / token decrypter can yield meaningful and informative error messages (with the proper concern for minimal information disclosure), which is currently somewhat hard to do.
The text was updated successfully, but these errors were encountered: