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
Currently, in the current_user functions from FastAPI/Flask/CLI integrations, we assume the token is valid and thus that the request to Fief will succeed.
However, there might be cases where the client considers the token as valid, but the Fief server does not. Typically, if we change our token structure and the client is outdated, the client will accept it but the server will reject.
We should handle this case more gracefully by raising a proper Unauthorized error when this happens.
The text was updated successfully, but these errors were encountered:
Currently, in the
current_user
functions from FastAPI/Flask/CLI integrations, we assume the token is valid and thus that the request to Fief will succeed.However, there might be cases where the client considers the token as valid, but the Fief server does not. Typically, if we change our token structure and the client is outdated, the client will accept it but the server will reject.
We should handle this case more gracefully by raising a proper Unauthorized error when this happens.
The text was updated successfully, but these errors were encountered: