Skip to content

Request for Keycloak Integration  #542

Closed

Description

@alexandre-meline

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

Activity

  1. arunrony commented on Dec 7, 2023

    @arunrony

    I am also interested in this feature and ready to provide insight and contribute if this gets considered.

  2. JamesCodeing commented on Dec 18, 2023

    @JamesCodeing

    I think this is one very good suggestion

  3. itamar82 commented on Mar 13, 2024

    @itamar82

    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.

  4. FermiParadox commented on Jan 26, 2025

    @FermiParadox

    Wouldn't Keycloak integration provide serious value to FastAPI?
    Saving 2k-6k $ is critical especially for small projects.

    • Login, permissions, password handling, email verification, 2FA, SSO, etc.
    • avoiding dozens of vulnerabilities
    • having it all tested

    Please @tiangolo check it out https://www.keycloak.org/

  5. jakob1379 commented on Dec 3, 2025

    @jakob1379

    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"

  6. nnWhisperer commented on Jan 1, 2026

    @nnWhisperer

    this is such an underrated comment; this project needs an OIDC support, as later one could easily add any provider AFAIU

    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"

  7. FermiParadox commented on Jan 19, 2026

    @FermiParadox

    Wouldn't Keycloak integration provide serious value to FastAPI? Saving 2k-6k $ is critical especially for small projects.

    * Login, permissions, password handling, email verification, 2FA, SSO, etc.
    
    * avoiding dozens of vulnerabilities
    
    * having it all tested
    

    Please @tiangolo check it out https://www.keycloak.org/

    A few more arguments I should mention:

    • used by:
      • Hitachi, CERN, Infosys (major Japanese pharmaceutical), etc. (link)
      • Accenture, Okta, Wayfair LLC, UnitedHealthcare, Hewlett-Packard Enterprise, Capgemini, etc. (Keycloak Community Survey) - check revenue :P
    • Keycloak is a Cloud Native Computing Foundation incubation project
    • 32k github stars
    • project lead Stian Thorgersen (Red Hat Senior Principal Software Engineer)

    “Hitachi is heavily using Keycloak because it is a critical part of API security,” said Yuichi Nakamura, Director, Hitachi, Ltd. “We also have long been contributing features for API security to Keycloak and are willing to help the Keycloak project to graduate the CNCF incubation process.” - 2023

    When it comes to developers building their own auth system, it is so easy to get massive security holes.

  8. locked and limited conversation to collaborators on Jan 22, 2026
  9. converted this issue into a discussion #2139 on Jan 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions