# SailPoint StrongDM SaaS Connector Documentation

> StrongDM SaaS Connector Documentation

# Documentation

# Connecting SailPoint and StrongDM SaaS

To connect SailPoint with StrongDM, perform the following tasks:

## Adding the Source in SailPoint

To connect to SailPoint, perform the following steps. Once the connection is made, you can configure it to meet your company's needs.

> [!IMPORTANT]
>
> By default, the provisioning feature is **disabled**, and the connector only supports read-only operations. To support provisioning operations, you must manually enable the feature in the source configuration.

**To configure a new source:**

1. Sign in to SailPoint.
2. Go to **Admin \> Connections \> Sources**.
3. Select **Create New**.
4. Search for the connector by entering the name in the search box, and then select **Configure**.
5. In the **Source Name** field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters.
6. In the **Description** field, provide additional details about the source to help distinguish it from similar sources. This field allows a maximum of 2,000 characters.
7. In the **Source Owner** field, begin typing the name of an owner. Matches appear after you type two or more letters. For more information, refer to [Assigning a Source Owner](<https://documentation.sailpoint.com/saas/help/sources/index.html#assigning-a-source-owner>).
8. (Optional) Select a governance group to grant its members [source](<https://documentation.sailpoint.com/saas/help/common/users/user_levels.html#source-sub-admin-user-level>) or [role](<https://documentation.sailpoint.com/saas/help/common/users/user_levels.html#role-sub-admin-user-level>) sub-admin level oversight of the source and its access. For more information, refer to [Creating and Managing Governance Groups](<https://documentation.sailpoint.com/saas/help/common/users/governance_groups.html>).
9. If this source represents a primary system containing your organization's personnel records, select the **Authoritative Source** checkbox. For more information, refer to [Creating Identity Profiles](<https://documentation.sailpoint.com/saas/help/setup/identity_profiles.html>).
10. Select **Continue**. The source is created, and you are navigated to the **Source Setup \> Base Configuration** page. Continue to configure your connected source there.

## Base Configuration

Provide the base configuration parameters. Information you entered in the Create New Source dialog is automatically entered into the fields in the Base Configuration page. You can edit this information if necessary.

1. Enter a unique name and description for the source.
2. In the **Source Owner** dropdown list, select the identity that owns this source.

   - To find a source owner, begin entering their name.
3. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider.

   > **Note**
   >
   > To add a credential provider, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](<https://documentation.sailpoint.com/connectors/help/credential_providers.html>).
4. Configure the authentication to allow SailPoint to connect to the source. Refer to [Connection Settings](<#connection-settings>) for more information.
5. (Optional) In the **Governance Group for Source Management** dropdown list, select a governance group to associate with this source. For more information about governance groups, refer to [Associating Governance Groups with a Source](<https://documentation.sailpoint.com/saas/help/common/users/governance_groups.html#associating-a-governance-group-with-a-source>).
6. (Optional) Choose whether to enable or disable provisioning for the source. Provisioning is disabled by default.

   - **Enable Provisioning** - Set the toggle to **Enabled** to allow the source to create, update, and deactivate accounts in the connected source system.
   - **Disable Provisioning** - Set the toggle to **Disabled** to disable provisioning for the source. Disabling provisioning will prevent the creation, updating, or deactivating of accounts on this source.
7. Select **Save**.

## Connection Settings

The following information is required for SailPoint to connect and interact with StrongDM.

> [!NOTE]
>
> **Screenshot**
>
> [![Connection Settings](<https://documentation.sailpoint.com/connectors/strongdm/saas/help/img/strongdm_conn_set.png>)](<https://documentation.sailpoint.com/connectors/strongdm/saas/help/img/strongdm_conn_set.png>)

1. Select **Connection Settings** from the menu.
2. Enter the **Base URL** for the StrongDM source.

   `https://app.strongdm.com/provisioning/generic/v2`
3. Enter the **API Token**. The API Token is the token used to access the StrongDM API. For more information on generating the API token, refer to [Prerequisites](<https://documentation.sailpoint.com/connectors/strongdm/saas/help/index.html#prerequisites>).
4. Select **Save**.

## Aggregation Settings

The following information is required for SailPoint to connect and interact with StrongDM.

> [!NOTE]
>
> **Screenshot**
>
> [![Aggregation Settings](<https://documentation.sailpoint.com/connectors/strongdm/saas/help/img/strongdm_agg.png>)](<https://documentation.sailpoint.com/connectors/strongdm/saas/help/img/strongdm_agg.png>)

1. Select **Aggregation Settings** from the menu on the left of the screen.
2. Enter the **Account Filter**.

   For example, `userName eq "someEmail@example.com"`
3. Enter the **Group Filter**.

   For example, `displayName eq "Engineering"`
4. Select **Save**.

## Review and Test

Perform a test to confirm the connection to SailPoint.

1. Go to **Review and Test**.
2. Confirm that the entries in each field are correct.

   If you note any mistakes, return to the section and make corrections.
3. Select **Test Connection**.

## SailPoint Application Onboarding

SailPoint application onboarding enables you to easily onboard new applications and create sources following the successful onboarding of a discovery source. To use this feature, continue to **Discovered Applications** in the SailPoint user interface.

For more information, refer to [Application Onboarding](<https://documentation.sailpoint.com/saas/help/ai/app_onboarding/index.html>) in the SailPoint SaaS documentation.

# Integrating SailPoint with StrongDM SaaS

StrongDM is a proxy that manages and audits access to databases, servers, clusters, and web apps. The StrongDM source manages Users and Groups from StrongDM.

This document is designed to give specific information about the requirements and fields needed to successfully configure an instance of the StrongDM source.

> [!NOTE]
>
> To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes](<https://community.sailpoint.com/release-notes/saas>) page.

## Supported Features

The StrongDM source supports the following features:

- Access Certifications (Certifications of entitlements connected to the accounts)
- Aggregate Accounts
- Aggregate Entitlements (Groups)
- Get Accounts
- Provisioning

  - Create Account
  - Add and Remove Entitlements (Groups)
  - Update Accounts
  - Enable Accounts
  - Disable Accounts
  - Delete Accounts

## Prerequisites

The following Prerequisites are required:

- To enable the generic SCIM connection and create a SCIM token, in the StrongDM Admin UI navigate to **Settings \> User Management \> Provisioning** and select the **Generic** provider option. Select **Activate** and then use the generated bearer token as the API Token. You will then use this API Token for authentication and authorization.
- In StrongDM, you must have the Administrator permission level.
- Refer to the following link for the [StrongDM SCIM API Specification](<https://www.strongdm.com/docs/architecture/scim-spec/>).

## Additional Information

This section describes the additional information related to StrongDM.

- StrongDM supports SCIM/REST and uses the following as a base url: `https://app.strongdm.com/provisioning/generic/v2`
- StrongDM uses a default page size of 100.

# Machine Account Attributes

## Machine Account Provisioning Attributes

The following table lists the attributes in the machine account creation template, including the generator and description for each attribute.

| Attribute | Generator | Description |
| --- | --- | --- |
| userName | Static | Username of the account |
| givenName | Static | First name of the account |
| familyName | Static | Last name of the account |
| active | Static | Active status of the account |

For more information, refer to [Machine Identity Security Overview](<https://documentation.sailpoint.com/saas/help/machine/index.html#implementing-without-application-data>).

# Provisioning

The StrongDM SaaS connector supports provisioning, allowing you to create and manage accounts and entitlements in StrongDM directly from SailPoint.

**Prerequisite:** Your system is configured for provisioning.

When SailPoint provisions new accounts to the source, it uses the attributes on the **Create Account** page as instructions or a template for what to include in the account. This page is also referred to as the *provisioning policy*.

When new access is granted on a source where a user does not already have an account, SailPoint automatically includes account creation in the provisioning. This applies whether provisioning is started from an access request or from an automated role or lifecycle state assignment.

For direct-connect sources, SailPoint automatically creates the account from this configuration. If the source is not configured as a direct-connect source, SailPoint creates and assigns a provisioning task to the source owner and includes the values for the source owner to use in manually creating the account.

> [!IMPORTANT]
>
> This section describes the default **Create Account** configuration. SailPoint recommends that you work with Services to define a provisioning configuration specific to your company's needs. Be sure to verify large changes to the provisioning policy before implementation. Failure to do so might cause provisioning to fail.

## Default Create Account Attributes

| Account Attribute | Generator | Description |
| --- | --- | --- |
| active | static true | Active status of the users |
| familyName | Identity Attribute - Last Name (lastname) | Last name of the user |
| givenName | Identity Attribute - First Name (firstname) | First name of the user |
| userName | Identity Attribute - Work Email | Unique Login Name of the user |

> [!NOTE]
>
> Upon account creation, the member will receive an invitation email to sign up and join the account.

# Schema Reference

The application schema is used to configure the objects returned from a connector.

> [!NOTE]
>
> - The **Account Schema** tab is used to define the attributes for each object type in the application being configured. The schema attributes can be defined as **Entitlement** or **Multi-Valued**. Refer to [Managing Source Account Schemas](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) for more information.
> - The schema attributes that are not present by [default](<#default-account-schema>) must be defined as strings if not specified.

The StrongDM SaaS connector uses the following default correlation and object configurations.

## Schema Objects

The following Schema Objects are supported:

### Account

Standard Account schema that manages StrongDM users.

- Discover Schema
- Aggregation
- Create
- Update
- Read
- Enable
- Disable

### Group

A group schema that manages groups on the StrongDM system.

- Aggregation
- Read

## Default Correlation Configuration

Before you aggregate accounts from this source, you can map account attributes with their corresponding identity attributes based on your requirements.

You can customize the correlation configuration. Refer to [Assigning Source Accounts to Identities](<https://documentation.sailpoint.com/saas/help/accounts/correlation.html>) for more information.

When you first create the StrongDM SaaS source, the default correlation mapping is:

| Account Attribute | Operation | Identity Attribute |
| --- | --- | --- |
| emails.work.primary | Equals | Work Email (email) |
| userName | Equals | SailPoint User Name (uid) |
| name.formatted | Equals | Name |

## Default Account Schema

Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location.

The set of account attributes each source stores and how they're organized is known as the account's *schema*. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to [Managing Source Account Schemas](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) for more information.

### Default Account Attributes

The StrongDM SaaS connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified.

| Attribute Name | Description |
| --- | --- |
| id | Unique key for user. |
| userName | Unique Login Name of the user. |
| name.formatted | Full name of the user. |
| name.familyName | Last name of the user. |
| name.givenName | First name of the user. |
| name.middleName | Middle name of the user. |
| displayName | Used to identify the relationship between the organization and the user. |
| active | Active status of the user. |
| emails.work.primary | Email address for the user. |
| emails.work.secondary | Email address for the user. |
| emails.home.primary | Email address for the user. |
| emails.home.secondary | Email address for the user. |
| emails.other.primary | Email address for the user. |
| emails.other.secondary | Secondary email address for the user. |
| nickname | The casual way to address the user in real life. |
| profileurl | A fully qualified URL pointing to a page representing the user's online profile. |
| title | The user's title, such as "Vice President." |
| preferredLanguage | Indicates the user's preferred written or spoken language. |
| locale | Used to indicate the user's default location. |
| timezone | The user's time zone in the 'Olson' time zone. |
| groups | Groups assigned to user. |
| employeeNumber | Numeric or alphanumeric identifier assigned to a person. |
| costCenter | Identifies the name of a cost center. |
| organization | Identifies the name of an organization. |
| division | Identifies the name of a division. |
| department | Identifies the name of a department. |
| manager.value | The ID of the SCIM resource representing the User's manager. REQUIRED |
| manager.displayName | Display name of the user's manager. |
| meta.created | Resource created date. |
| meta.lastModified | Resource last modified date. |
| meta.location | The user's location. |
| meta.resourceType | The user's resource type. |

## Default Entitlement Attributes

Entitlement attributes define the entitlements, such as groups or roles, that can be assigned to the managed system's user accounts. Refer to [Managing Entitlements](<https://documentation.sailpoint.com/saas/help/access/entitlements.html>) for more information.

> [!CAUTION]
>
> Changing the attribute marked as the Entitlement ID after aggregating accounts or entitlements can result in duplicate entitlements being created, or access profiles and roles breaking. To avoid this, edit the entitlement schema before performing any aggregations.

| Attribute Name | Description |
| --- | --- |
| id | Unique ID of the user. |
| displayName | DisplayName of the user. |
| members | List of user's belongs to the group. |

# Troubleshooting

If you encounter any of the following issues or errors, SailPoint recommends that you follow the guidance provided below to resolve the error before contacting SailPoint Support.

For issues or errors that are not addressed in this connector guide, refer to the following resources for troubleshooting information:

- [SailPoint Identity Services Documentation](<https://documentation.sailpoint.com/saas/help/index.html>)
- [SailPoint Support Knowledge Base](<https://support.sailpoint.com/csm?id=kb_view2&amp;kb_id=05ff44289f011200550bf7b6077fcfa3>)
- [SailPoint Developer Community](<https://developer.sailpoint.com/>)

## Debug Logs

For information about managing additional source settings, including debug logging and downloading connector logs, refer to [Managing Additional Settings](<https://documentation.sailpoint.com/saas/help/sources/managing_additional_settings.html>).

## Points to Consider During Provisioning

- emails.work.primary attribute

  - To provision the **emails.work.primary** attribute you must update the **userName** attribute. StrongDM managed systems do not support direct updates of the **emails.work.primary** attribute.
- IdentityAliases attribute

  - The data type for the IdentityAliases attribute is **String** type only. The supported use cases are `"default,something"` and

    `""default,something",""xgeneric,somethingelse""`
  - If the IdentityAliases attribute sync fails, ensure the attribute value is not `""default,something",""default,somethingelse""`. This value is not supported as it will replace a later used value in the managed system. SailPoint provisions the exact value provided as input, ie; the below example attribute IdentityAliases will set the value as `["default,x511427"]` in the managed system.

    ```text
    identityAliases = "default,something"
    ```