> For the complete documentation index, see [llms.txt](https://docs.authgear.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.authgear.com/get-started/single-sign-on-with-saml/use-authgear-as-saml-identity-provider-for-pipedrive.md).

# Use Authgear as SAML Identity Provider for Pipedrive

Guide on how to use Authgear as a SAML IdP for Pipedrive

Security Assertion Markup Language (SAML) is a standard that allows an Identity Provider (IdP) and a Service Provider (SP) to perform user authentication and authorization without exchanging a user's password.

In this post, you'll learn how to set up Authgear as an Identity Provider and Pipedrive as a Service Provider.

### Prerequisites

* An Authgear account. Sign up for free.
* Email login enabled in your Authgear project. Pipedrive identifies users by email address, so every user who signs in to Pipedrive needs one.
* A Pipedrive account with admin access. SAML single sign-on is available on all Pipedrive plans.

### Step 1: Get the SAML Settings from Pipedrive

Log in to Pipedrive and go to **Settings** > **Security center** > **Single sign-on**.

The **SAML configuration for your Identity Provider (IDP)** section lists the values Authgear needs. Note the following:

* **Metadata url**, for example `https://<your-company>.pipedrive.com/sso/auth/samlp/metadata.xml`
* **Single Sign On (SSO) url**, for example `https://<your-company>.pipedrive.com/sso/auth/samlp`

Keep this page open. You'll come back to it in Step 5.

### Step 2: Create an Authgear Client Application

You need an Authgear client application with SAML 2.0 support to use Authgear as a SAML identity provider.

1. Log in to Authgear Portal, select your project, and go to **Applications**.
2. Click **Add Application**.
3. Enter a **Name** for the application, for example `Pipedrive`.
4. Under **Framework**, in the **Other** section, select **Other OIDC/SAML compatible**.
5. Click **Create application**.

The application opens on its **Quick Start** tab.

{% hint style="info" %}
Only applications created with **Other OIDC/SAML compatible** have a **SAML 2.0** tab. To reuse an existing application, check that it has this tab, then skip to Step 3.
{% endhint %}

### Step 3: Enable SAML 2.0 in Client Application

In your Authgear client application, open the **SAML 2.0** tab and turn on **SAML 2.0 Support**.

Then configure the following:

* **NameID Format**: `urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified`
* **User attribute for NameID**: **Email**
* **Allowed Assertion Consumer Service URLs (ACS URLs)**: the Pipedrive **Single Sign On (SSO) url** from Step 1, for example `https://<your-company>.pipedrive.com/sso/auth/samlp`
* **Assertion Audience**: the Pipedrive **Metadata url** from Step 1, for example `https://<your-company>.pipedrive.com/sso/auth/samlp/metadata.xml`

Leave **Response Destination** and **Subject Recipient** empty.

{% hint style="info" %}
Pipedrive shows `pipedrive` as its **Issuer**, but the **Assertion Audience** field in Authgear only accepts a URL. Use the Pipedrive **Metadata url** instead.
{% endhint %}

Click on **Save** to keep your changes.

### Step 4: Send the Email Attribute

Pipedrive requires an `Email` attribute in the SAML assertion. Add it with [SAML Attribute Mapping](https://docs.authgear.com/get-started/single-sign-on-with-saml/saml-attribute-mapping.md).

In Authgear Portal, go to **Advanced** > **Edit Config**. Under `saml.service_providers`, find the entry whose `client_id` matches your client application, and add the following `attributes` block:

```yaml
saml:
  service_providers:
  - client_id: YOUR_CLIENT_ID
    # ...existing fields, leave as-is...
    attributes:
      definitions:
      - name: Email
      mappings:
      - from:
          user_profile:
            pointer: /email
        to:
          saml_attribute: Email
```

Save the config.

### Step 5: Add Authgear SAML IdP in Pipedrive

Go back to your client application's **SAML 2.0** tab in Authgear Portal. In the **Identity Provider Certificates** section, click **Download Certificate**.

In the Pipedrive **Single sign-on** page, fill in the **SAML configuration for Pipedrive** section:

* **Issuer**: the **Identity Provider Metadata** URL from Authgear, for example `https://<your-project>.authgear.cloud/saml2/metadata/<client-id>`
* **Single Sign On (SSO) url**: the **Login URL** from Authgear, for example `https://<your-project>.authgear.cloud/saml2/login/<client-id>`
* **X.509 certificate**: open the Identity Provider Certificate you downloaded, and paste its full content, including the `-----BEGIN CERTIFICATE-----` and `-----END CERTIFICATE-----` lines.

{% hint style="info" %}
Pipedrive only accepts a URL in the **Issuer** field, so use the **Identity Provider Metadata** URL, not the `urn:` value shown as **Issuer** in Authgear.
{% endhint %}

Click **Save changes**.

### Step 6: Test and Enable Single Sign-on

Click **Test** on the Pipedrive **Single sign-on** page. You should be redirected to the Authgear login page. Log in with an Authgear account whose email address matches a user in your Pipedrive company.

Once the test succeeds, turn on **Enable for users** and click **Save changes**. Your Pipedrive users can now log in using Authgear.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.authgear.com/get-started/single-sign-on-with-saml/use-authgear-as-saml-identity-provider-for-pipedrive.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
