Handle FiefRequestError gracefully in current_user integrations
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.
fief-dev / fief-python
Fief client for Python
12
Contributors get 80% of received funds after fees
How does funding with Polar work?
1
Pay now to fund the work behind this issue.
2
Get updates on progress being made.
3
Maintainer is rewarded once the issue is completed.
FAQ
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too