> For the complete documentation index, see [llms.txt](https://docs.caf.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.caf.io/caf-docs/user-guide/organizations/sso-configurations/generic.md).

# Generic Provider (SAML / OIDC)

Configure SSO with any SAML or OIDC compatible provider.

This guide explains how to configure SSO between Organizations and any identity provider compatible with `SAML 2.0` or `OpenID Connect` (`OIDC`). Use it for providers such as Keycloak, OneLogin, PingFederate, **Microsoft Entra ID (OIDC)**, and others.

{% hint style="info" %}
**Before you begin:** Open **Authentication** → **SSO** in Organizations and copy the **Entity ID** and **ACS URL** (SAML) or **Redirect URI** (OIDC) as described in [Step 2 of the SSO Configuration Guide](/caf-docs/user-guide/organizations/sso-configurations.md#step-2-enable-sso-and-configure-the-provider).
{% endhint %}

***

## Prerequisites

* Super Admin access to Organizations
* Administrator access to the identity provider
* Provider compatible with `SAML 2.0` or `OpenID Connect` / `OAuth 2.0`

***

## Choose the Protocol

{% tabs %}
{% tab title="SAML" %}

## SAML Configuration

### Create Application in the Provider

1. Create a new `SAML 2.0` application or integration.
2. Set the **ACS URL** to the **ACS URL** copied from Organizations.
3. Set the **Entity ID** / **Audience** to the **Entity ID** copied from Organizations.

### Configure Attribute Statements

Map attributes your provider will send to Organizations:

| Name (example) | Typical source |
| -------------- | -------------- |
| `email`        | User email     |
| `name`         | Display name   |
| `given_name`   | First name     |
| `family_name`  | Last name      |

### Configure Group Attribute (Optional)

When you use **Group assignment rules** based on IdP groups:

| Name (example) | Value                                             |
| -------------- | ------------------------------------------------- |
| `groups`       | User group membership (format varies by provider) |

### Get Metadata

Copy the provider **Metadata URL**, or download the metadata XML and paste it in Organizations when URL hosting is not available.

{% hint style="warning" %}
Confirm exact SAML attribute names with your provider documentation, then enter them on the **Attribute mapping** tab in Organizations. Some providers (including Microsoft Entra ID) use long claim URIs such as `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress` instead of short names like `email`.
{% endhint %}
{% endtab %}

{% tab title="OIDC" %}

## OIDC Configuration

### Create Application in the Provider

1. Create a `Web` or `Server-side` OIDC client.
2. Set **Grant type** to Authorization Code.
3. Add the **Redirect URI** copied from Organizations.

### Get Provider Credentials

| Provider field    | Description                                   |
| ----------------- | --------------------------------------------- |
| **Client ID**     | Application identifier                        |
| **Client Secret** | Confidential client secret                    |
| **Issuer URL**    | Provider issuer (discovery endpoint base URL) |

{% hint style="info" %}
The issuer is usually listed at `/.well-known/openid-configuration`.
{% endhint %}

### Request method

After saving OIDC settings in Organizations, set **Request method** to **GET** (default) or **POST** based on your provider documentation. See [OIDC request method](/caf-docs/user-guide/organizations/sso-configurations.md#oidc-request-method-get-vs-post) in the SSO Configuration Guide.
{% endtab %}
{% endtabs %}

***

## Next Steps

Return to the [Organizations SSO Configuration Guide](/caf-docs/user-guide/organizations/sso-configurations.md) to:

1. [Enable SSO and paste provider settings](/caf-docs/user-guide/organizations/sso-configurations.md#step-2-enable-sso-and-configure-the-provider)
2. [Configure attribute mapping](/caf-docs/user-guide/organizations/sso-configurations.md#step-3-configure-attribute-mapping)
3. [Configure group assignment rules](/caf-docs/user-guide/organizations/sso-configurations.md#step-4-configure-group-assignment-rules)
4. [Save and test](/caf-docs/user-guide/organizations/sso-configurations.md#step-5-save-and-test)

***

## Troubleshooting

| Problem                    | Probable cause               | Solution                                      |
| -------------------------- | ---------------------------- | --------------------------------------------- |
| Redirect error             | URI mismatch                 | Match **ACS URL** or **Redirect URI** exactly |
| Invalid token (OIDC)       | Wrong client secret          | Regenerate secret and update Organizations    |
| Invalid certificate (SAML) | Expired certificate          | Update metadata in Organizations              |
| Claims not received        | Missing scopes or attributes | Add OIDC scopes or SAML attribute statements  |
| Invalid issuer             | Wrong issuer URL             | Validate `/.well-known/openid-configuration`  |
| Signature error (SAML)     | Stale metadata               | Refresh metadata URL or XML in Organizations  |

***

## References

* [OpenID Connect Specification](https://openid.net/connect/)
* [OAuth 2.0 RFC](https://datatracker.ietf.org/doc/html/rfc6749)
* [SAML 2.0 Specification](https://docs.oasis-open.org/security/saml/v2.0/)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.caf.io/caf-docs/user-guide/organizations/sso-configurations/generic.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.