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
Initially we went down the path of using FastAPI JWT Auth a well implemented authentication layer for FastAPI, which also handles CSRF. Dependabot raised concerns around the version of PyJWT that's referenced by this project.
The project looks abandoned, with several pull requests that have been ignored for a while. To follow up I attempted to contact the maintainer of the project and did not hear back from him.
We had aspirations of standardising on this library with tickets to document the patterns in #34#33 and #25
Given these facts it would be unwise to standardise on the library and revert back to implementing our own solution.
The team at Anomaly had used fastapi-csrf-protect in the past, it would also be recommended to study the relevance of this implementation before deciding to use it.
FastAPI docs have many guides around the security measures. As such at the moment we are closing the above tickets and continuing with our own implementation.
Initially we went down the path of using FastAPI JWT Auth a well implemented authentication layer for FastAPI, which also handles
CSRF
. Dependabot raised concerns around the version ofPyJWT
that's referenced by this project.The project looks abandoned, with several pull requests that have been ignored for a while. To follow up I attempted to contact the maintainer of the project and did not hear back from him.
We had aspirations of standardising on this library with tickets to document the patterns in #34 #33 and #25
Given these facts it would be unwise to standardise on the library and revert back to implementing our own solution.
The team at Anomaly had used fastapi-csrf-protect in the past, it would also be recommended to study the relevance of this implementation before deciding to use it.
FastAPI docs have many guides around the security measures. As such at the moment we are closing the above tickets and continuing with our own implementation.
Resources:
The text was updated successfully, but these errors were encountered: