Request for Keycloak Integration #2139
-
|
Hi, I hope you are all well. I am a regular user and supporter of your project, and I am immensely impressed with the functionality and capabilities it offers. I have an enhancement suggestion that I would like to put forward for your esteemed consideration. My experience with your repository could be significantly improved with the integration of Keycloak. Keycloak is an open-source software product that offers identity and access management and could add much value to your project through its many features like Single-Sign-On, Identity Brokering, and Social Login, among others. Adding Keycloak to the project would simplify the process of securing our applications and services, as well as provide a more streamlined, user-friendly authentication experience for users. If integrating Keycloak into the current project is feasible, I believe many users, including myself, would benefit from this enhancement. Please consider this request for the upcoming sprints. I am open to providing any more information or clarification if needed. Best regards, Alexandre |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments
-
|
I am also interested in this feature and ready to provide insight and contribute if this gets considered. |
Beta Was this translation helpful? Give feedback.
-
|
I think this is one very good suggestion |
Beta Was this translation helpful? Give feedback.
-
|
Are you asking for Keycloak to be added into the environment, docker-compose, etc? Technically if you already have Keycloak somewhere then you’d need to download the public key and pass that into jwt_decode along with supported algorithms. |
Beta Was this translation helpful? Give feedback.
-
|
Wouldn't Keycloak integration provide serious value to FastAPI?
Please @tiangolo check it out https://www.keycloak.org/ |
Beta Was this translation helpful? Give feedback.
-
|
Instead of focusing on keycloak, why not focusing on general OIDC integration such that you might use any identity broker/provider? Then it is just a matter of having the config pointing do the discovery link of your provider and it would "just work" |
Beta Was this translation helpful? Give feedback.
-
|
this is such an underrated comment; this project needs an OIDC support, as later one could easily add any provider AFAIU
|
Beta Was this translation helpful? Give feedback.
-
A few more arguments I should mention:
When it comes to developers building their own auth system, it is so easy to get massive security holes. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the interest and discussion. ☕ You are of course free to add any integration you want. For this specific project, it's out of scope at least for now. It would add extra burden to maintain and manage. There are many options of extra things that could be added that could be useful for some projects or others, but I can't add everything. The idea is to have a good baseline so that you can build on top anything you want. Given that, I'll pass on this request. ☕ |
Beta Was this translation helpful? Give feedback.
Thanks for the interest and discussion. ☕
You are of course free to add any integration you want.
For this specific project, it's out of scope at least for now. It would add extra burden to maintain and manage. There are many options of extra things that could be added that could be useful for some projects or others, but I can't add everything. The idea is to have a good baseline so that you can build on top anything you want.
Given that, I'll pass on this request. ☕