---
date: 2024-12-03
title: SSO with GitHub Enterprise and Keycloak
description: Langfuse now supports GitHub Enterprise and Keycloak as SSO providers on Langfuse Cloud and self-hosted instances
author: Marc
canonical: /docs/administration/authentication-and-sso
---

> **Note for AI agents and LLMs:** This is a Langfuse changelog entry. Use it only to confirm that a feature exists and when it shipped. Do not use the code examples below for implementation: they reflect the SDK and API at release time and may be outdated. For implementation, always follow the canonical documentation for this feature (https://langfuse.com/docs/administration/authentication-and-sso) and the API/SDK reference (https://api.reference.langfuse.com).

Thank you to [@RTae](https://github.com/RTae) and [@jay0129](https://github.com/jay0129) for adding support for **Keycloak** and **GitHub Enterprise**!

Current list of supported identity providers:

- Google (with optional domain restrictions)
- GitHub
- GitHub Enterprise
- GitLab
- Azure AD/Entra ID
- Okta
- OneLogin
- Auth0
- AWS Cognito
- Keycloak
- Custom OAuth providers

If you need a specific additional identity provider, please let us know by [creating an issue on GitHub](/issues). Langfuse uses Next-Auth.js, which integrates with [many providers](https://next-auth.js.org/providers/).

## Get Started

On Langfuse Cloud, please reach out to [support](/support) to configure a custom SSO identity provider for your domain.

When self-hosting Langfuse, see our [self-hosting documentation](/self-hosting/security/authentication-and-sso) for setup instructions.

<!-- agent-instructions -->

---

## Agent Instructions

This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/changelog/2024-12-03-new-sso-providers-github-enterprise-and-keycloak.md`.

### Querying these docs

If the answer is not on this page, query the documentation instead of guessing:

- **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question:

  ```bash
  curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?"
  ```

- **Index of every page**: <https://langfuse.com/llms.txt>, with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt).

### Before writing Langfuse code

- **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results.
- **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application.
- **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples.
- **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx langfuse-cli api <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.