> ## Documentation Index > Fetch the complete documentation index at: https://formbricks.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Setup SAML with Identity Providers > This guide explains the settings you need to use to configure SAML with your Identity Provider. Once configured, obtain an XML metadata file and use it to configure SAML in Formbricks. ### SAML Registration with Identity Providers This guide explains the settings you need to use to configure SAML with your Identity Provider. Once configured, obtain an XML metadata file and use it to configure SAML in Formbricks. > **Note:** Please do not add a trailing slash at the end of the URLs. Create them exactly as shown below. **Assertion consumer service URL / Single Sign-On URL / Destination URL:** [https://app.formbricks.com/api/auth/saml/callback](https://app.formbricks.com/api/auth/saml/callback) **Entity ID / Identifier / Audience URI / Audience Restriction:** [https://saml.formbricks.com](https://saml.formbricks.com) > **Note:** [https://saml.formbricks.com](https://saml.formbricks.com) is hardcoded in Formbricks — do not replace it with your instance URL. It is the fixed SP Entity ID and must match exactly as shown in SAML assertions. **Response:** Signed **Assertion Signature:** Signed **Signature Algorithm:** RSA-SHA256 **Assertion Encryption:** Unencrypted **NameID Format:** EmailAddress **Application username:** email **Mapping Attributes / Attribute Statements:** * Name claim: If your IdP has a `name` claim, set the following claims to populate the name field: | Name | Name Format | Value | | ---- | ----------- | --------- | | name | Basic | user.name | Many IdPs do not have a `name` claim. If not, you can use different claims to populate the name field. The order of precedence is `name` -> **other options** -> `email`. **Other options:** | Name | Name Format | Value | | --------- | ----------- | --------------------------- | | firstName | Basic | **FIRST\_NAME\_EQUIVALENT** | | lastName | Basic | **LAST\_NAME\_EQUIVALENT** | Refer to the table below for the different claims you can use for each IdP. | IdP | FIRST\_NAME\_EQUIVALENT | LAST\_NAME\_EQUIVALENT | | ----------------------------- | --------------------------------- | --------------------------------- | | Okta | user.firstName | user.lastName | | Microsoft Entra ID (Azure AD) | user.givenName | user.surname | | Google Workspace | user.given\_name / user.firstName | user.family\_name / user.lastName | | OneLogin | user.FirstName / user.first\_name | user.LastName / user.last\_name | | Auth0 | user.given\_name | user.family\_name | | JumpCloud | user.firstname | user.lastname | Above provided claims may differ based on your configuration and the IdP you are using. Please refer to the documentation of your IdP for the correct claims. ### SAML With Okta For example, in Okta, once you create an account, you can click on Applications on the sidebar menu:

* **Single Sign-On URL**: `https:///api/auth/saml/callback` or `http://localhost:3000/api/auth/saml/callback` (if you are running Formbricks locally) * **Audience URI (SP Entity ID)**: `https://saml.formbricks.com` (hardcoded; do not replace with your instance URL)

That's it. Now when you try to login with SSO, your application on Okta will handle the authentication.