# SSO With Shibboleth

### Steps

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

{% tabs %}
{% tab title="US" %}
**Create an application in Shibboleth**

1. Sign in to your Shibboleth Identity Provider (IdP) admin console.
   * For Shibboleth IdP version 4 and higher, OIDC configuration is managed through the [OIDC OP Extension](https://shibboleth.atlassian.net/wiki/spaces/IDPPLUGINS/pages/1265631776/OIDC+OP).
2. Register a new OIDC client:
   * **Redirect URI:**

     ```
     https://app.strongdm.com/sso/callback
     ```
   * **Grant type:** Authorization Code
   * **Response type:** code
   * **Scopes:** `openid email profile`
3. Record the generated **Client ID** and **Client Secret**.
4. Configure the attribute release consent so that the ID Token or UserInfo endpoint includes:
   * `email` (required)
   * `name` (recommended)
   * `groups` (optional, for role mapping)
     {% 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.*

**Create an application in Shibboleth**

1. Sign in to your Shibboleth Identity Provider (IdP) admin console.
   * For Shibboleth IdP version 4 and higher, OIDC configuration is managed through the [OIDC OP Extension](https://shibboleth.atlassian.net/wiki/spaces/IDPPLUGINS/pages/1265631776/OIDC+OP).
2. Register a new OIDC client:
   * **Redirect URI:**

     ```
     https://app.uk.strongdm.com/sso/callback
     ```
   * **Grant type:** Authorization Code
   * **Response type:** code
   * **Scopes:** `openid email profile`
3. Record the generated **Client ID** and **Client Secret**.
4. Configure the attribute release so that the ID Token or UserInfo endpoint includes:
   * `email` (required)
   * `name` (recommended)
   * `groups` (optional, for role mapping)
     {% 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.*

**Create an application in Shibboleth**

1. Sign in to your Shibboleth Identity Provider (IdP) admin console.
   * For Shibboleth IdP version 4 and higher, OIDC configuration is managed through the [OIDC OP Extension](https://shibboleth.atlassian.net/wiki/spaces/IDPPLUGINS/pages/1265631776/OIDC+OP).
2. Register a new OIDC client:
   * **Redirect URI:**

     ```
     https://app.eu.strongdm.com/sso/callback
     ```
   * **Grant type:** Authorization Code
   * **Response type:** code
   * **Scopes:** `openid email profile`
3. Record the generated **Client ID** and **Client Secret**.
4. Configure the attribute release so that the ID Token or UserInfo endpoint includes:
   * `email` (required)
   * `name` (recommended)
   * `groups` (optional, for role mapping)
     {% endtab %}
     {% endtabs %}

#### Configure in StrongDM

1. Log in to the StrongDM Admin UI.
2. Go to **Settings > User Management > Single Sign-on**.
3. Set **Enable single sign-on?** to **Yes**.
4. Choose **Shibboleth** from the **Provider** dropdown.
5. Enter the following information:
   * **Single sign-on URL:** Your Shibboleth IdP’s authorization endpoint. For example:

     ```
     https://idp.example.org/idp/profile/oidc/authorize
     ```
   * **Client ID:** Your client ID from Shibboleth
   * **Client Secret:** Your client secret from Shibboleth
6. (Optional) Configure additional settings as desired, and then **Save.**


---

# Agent Instructions: 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:

```
GET https://docs.strongdm.com/admin/principals/sso/sso-with-shibboleth.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.