> For the complete documentation index, see [llms.txt](https://docs.strongdm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.strongdm.com/admin/principals/sso/adfs-oidc.md).

# SSO With ADFS

This guide provides step-by-step instructions on how to configure single sign-on (SSO) with Active Directory Federated Services (ADFS). You already use ADFS to conveniently manage permissions to applications. After SSO configuration is complete, you'll be able to use ADFS to manage permissions to your databases.

### Prerequisites

Your ADFS server will need a valid TLS certificate.

{% hint style="info" %}
These instructions vary based on your organization's StrongDM region (not your individual location).
{% endhint %}

### Steps

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

1. Within Application Groups, add a new application group. From the Application Group Wizard's **Welcome** screen, select the client-server application template **Server application accessing a web API**. Provide a name and click **Next**.

   ![](/files/K1bvZf7Dt1Oy6ojWw3Cb)
2. In **Server application**, you'll be configuring the server application redirect URI. Save the client identifier; you will need this in the following steps. Add the redirect URI depending on your tenant location: `https://app.strongdm.com/auth/return`.
3. In **Configure Application Credentials**, select the checkbox for **Generate a shared secret** and save the secret for later.
4. In **Configure Web API**, add the client identifier you saved from the previous step.
5. In **Configure application permissions**, select the checkboxes for the following scope names:
   1. allatclaims
   2. aza
   3. email
   4. openid
   5. profiile
6. In **Summary**, review the settings and click **Next**.
7. From the Add Transform Claim Rule Wizard's **Configure Claim Rule** screen, enable login by email instead of UPN. By default StrongDM will match your login email address to the UPN returned by ADFS. If you would prefer to use email, edit the Web API and add the following transformation rule as shown.

   ![](/files/oNjCN8Oh6ftBRy3YdCvi)
8. Next, enable ADFS in the StrongDM Admin UI in **Settings** > [User Management](https://app.strongdm.com/app/settings/user-management). Click the **lock** to make changes, and then select **Active Directory** from the provider drop-down menu. Add your client details as shown and click **activate**.

   ![](/files/LmvpxHREcDN235P3XwwC)
   {% endtab %}

{% tab title="UK" %}
*Follow instructions in the tab for the region of your organization's StrongDM control plane, not your own location. The default control plane region is US.*

* Within Application Groups, add a new application group. From the Application Group Wizard's **Welcome** screen, select the client-server application template **Server application accessing a web API**. Provide a name and click **Next**.

  ![](/files/K1bvZf7Dt1Oy6ojWw3Cb)
* In **Server application**, you'll be configuring the server application redirect URI. Save the client identifier; you will need this in the following steps. Add the redirect URI depending on your tenant location: `https://app.uk.strongdm.com/auth/return`.
* In **Configure Application Credentials**, select the checkbox for **Generate a shared secret** and save the secret for later.
* In **Configure Web API**, add the client identifier you saved from the previous step.
* In **Configure application permissions**, select the checkboxes for the following scope names:
  1. allatclaims
  2. aza
  3. email
  4. openid
  5. profiile
* In **Summary**, review the settings and click **Next**.
* From the Add Transform Claim Rule Wizard's **Configure Claim Rule** screen, enable login by email instead of UPN. By default StrongDM will match your login email address to the UPN returned by ADFS. If you would prefer to use email, edit the Web API and add the following transformation rule as shown.

  ![](/files/oNjCN8Oh6ftBRy3YdCvi)
* Next, enable ADFS in the StrongDM Admin UI in **Settings** > [User Management](https://app.strongdm.com/app/settings/user-management). Click the **lock** to make changes, and then select **Active Directory** from the provider drop-down menu. Add your client details as shown and click **activate**.

  ![](/files/LmvpxHREcDN235P3XwwC)
  {% endtab %}

{% tab title="EU" %}
*Follow instructions in the tab for the region of your organization's StrongDM control plane, not your own location. The default control plane region is US.*

* Within Application Groups, add a new application group. From the Application Group Wizard's **Welcome** screen, select the client-server application template **Server application accessing a web API**. Provide a name and click **Next**.

  ![](/files/K1bvZf7Dt1Oy6ojWw3Cb)
* In **Server application**, you'll be configuring the server application redirect URI. Save the client identifier; you will need this in the following steps. Add the redirect URI depending on your tenant location: `https://app.eu.strongdm.com/auth/return`.
* In **Configure Application Credentials**, select the checkbox for **Generate a shared secret** and save the secret for later.
* In **Configure Web API**, add the client identifier you saved from the previous step.
* In **Configure application permissions**, select the checkboxes for the following scope names:
  1. allatclaims
  2. aza
  3. email
  4. openid
  5. profiile
* In **Summary**, review the settings and click **Next**.
* From the Add Transform Claim Rule Wizard's **Configure Claim Rule** screen, enable login by email instead of UPN. By default StrongDM will match your login email address to the UPN returned by ADFS. If you would prefer to use email, edit the Web API and add the following transformation rule as shown.

  ![](/files/oNjCN8Oh6ftBRy3YdCvi)
* Next, enable ADFS in the StrongDM Admin UI in **Settings** > [User Management](https://app.strongdm.com/app/settings/user-management). Click the **lock** to make changes, and then select **Active Directory** from the provider drop-down menu. Add your client details as shown and click **activate**.

  ![](/files/LmvpxHREcDN235P3XwwC)
  {% endtab %}
  {% endtabs %}


---

# 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.strongdm.com/admin/principals/sso/adfs-oidc.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.