# SailPoint SOTI MobiControl Connector Documentation

> SOTI MobiControl Connector Documentation

# Documentation

# Connecting SailPoint and SOTI MobiControl

To connect SailPoint to the source, perform the following tasks:

## Adding and Configuring 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.

1. Go to **Admin \> Connections \> Sources**.
2. Select **Create New**.
3. Search for a source type and select **Actions**.
4. In the **Actions** dropdown, select the setup method:

   - **Express Setup** - Quickly create a read-only connection to your target system by providing minimal configurations and authentication. On completion, aggregation is automatically started.

     > **Note**
     >
     > Express Setup supports Credential Providers. For information on supported credential providers and configuration, refer to [Credential Providers](<https://documentation.sailpoint.com/connectors/help/credential_providers.html>). For more information, contact your SailPoint Customer Service Manager.
   - **Standard Setup** - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup.

### Express Setup

1. Review the directions and select **Start Express Setup**.
2. Review the pre-populated source name, source owner, and description. To update, select **Edit**.

   > **Note**
   >
   > Source name must be unique.
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 in SailPoint, 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. For more information, refer to the **Connection Settings** page.
5. Select **Finish**. After a successful test connection, the system creates your source and prompts you to run an aggregation.

   - If you want to aggregate now, select **Aggregate**.

     - To see the latest account aggregation history, go to **Account Management \> Account Aggregation**.
     - To see the list of aggregated source accounts, go to **Account Management \> Accounts**.
   - If you want to aggregate later, select **Exit**. This returns you to the **Sources** page. Your new source is listed, but contains no accounts or aggregation history yet.

### Standard Setup

Configure more detailed settings relative to Express Setup.

1. In the **Source Name** field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters.
2. 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.
3. 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>).
4. (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>).
5. 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>).
6. Select **Continue**. The source is created, and you are navigated to the **Source Setup \> Base Configuration** page. Here, continue to configure your connected source.

## 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 descriptive **Source Name** for the connection.
2. Enter the **Source Description** that provides details necessary to distinguish it from similar connection sources.
3. In **Source Owner**, begin typing the name of the source owner.
4. (Optional) Select the appropriate **Governance Group for Source Management** from the dropdown list. 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>).
5. Select **Create Manual Work Items** to enable the source to support additional source management features such as creating accounts and access profile management.

   > **Important**
   >
   > Once you enable this feature, it can't be disabled.

   For more information on manual work items, refer to [Work Items](<https://developer.sailpoint.com/docs/api/work-items>). For more information on SailPoint features, refer to [SailPoint Identity Services](<https://documentation.sailpoint.com/saas/help/index.html>).
6. Select **Save**.

## Connection Settings

Configure a secured, direct connection to the source.

1. Select **OAuth 2.0 ROPC** as the **Authentication Type**.
2. Enter the SOTI MobiControl API base URL as **Base URL**. For example, `https://<your-tenant>.mobicontrol.cloud/MobiControl/api`. Do not include a trailing slash.
3. Enter the OAuth token endpoint as **Token URL**. For example, `https://<your-tenant>.mobicontrol.cloud/MobiControl/api/token`.
4. Enter **Client ID**.
5. Enter **Client Secret**.
6. Enter the MobiControl administrator account username as **Administrator Username**.
7. Enter the MobiControl administrator account password as **Administrator Password**.
8. 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 SOTI MobiControl

SOTI MobiControl is an enterprise mobility management platform that helps organizations deploy, manage, monitor, and secure mobile devices and applications across their workforce. The SOTI MobiControl connector is a read-only integration that enables SailPoint to aggregate local and SSO user accounts and security role entitlements for identity governance and quick compliance use cases. This document provides the instructions required to configure a new direct connection between SailPoint and SOTI MobiControl. For a reference to the terminology specific to SailPoint products, refer to [Source and Connector Definitions](<https://documentation.sailpoint.com/saas/help/sources/index.html#source-and-connector-definitions>).

> [!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 SOTI MobiControl connector supports the following:

### Account Management

- Aggregate Users (local and SSO)

### Entitlement Management

- Aggregate Security Roles

> [!IMPORTANT]
>
> Quick Compliance connectors have the following manual aggregation limits within a 24-hour period:
>
> - **Organization Admins**: Limited to 3 manual account or entitlement aggregations per day per source. This limit is cumulative across all admins in the organization.
> - **Regular Users**: Limited to 1 manual account or entitlement aggregation per day per source.
>
> These limits ensure that individual compliance statuses are kept up to date while maintaining continuous compliance monitoring. If you need to run additional aggregations beyond these limits, contact SailPoint Support.

### Pagination

The SOTI MobiControl source uses `skip` and `take` query parameters for offset-based pagination. The connector starts at `skip=0` (0-indexed) and increments `skip` after each request. Aggregation continues until the API returns an empty array, at which point aggregation terminates.

#### How Pagination Works for This Operation

- **Initial Page Offset:** `0` - starting point for the first request (SOTI MobiControl offsets are 0-indexed via the `skip` query parameter).
- **Page Size:** `100` - number of records requested per page, passed via the `take` query parameter.

Paging steps:

- `$limit$` = `100`
- `TERMINATE_IF $RECORDS_COUNT$ = 0`
- `$offset$` = `$offset$ + $limit$`
- `$endpoint.fullUrl$` = `$application.baseUrl$` + `"/security/principal/users?skip=" + $offset$ + "&take=" + $limit$`

## Prerequisites

Before configuring the SOTI MobiControl connector, ensure the following requirements are met:

1. Know your MobiControl tenant hostname. For example, if your dashboard URL is `https://acme.mobicontrol.cloud`, your tenant hostname is `acme`.
2. Have an API client ID and client secret.
3. Have a MobiControl administrator account (not an IdP user) with credentials for the connector.

### Create an API Client

To create an API client:

1. Sign in to the MobiControl dashboard.
2. Go to **Global Settings**.
3. On the **Services** tab, select **API Client**.
4. Create a new API client with `grant_type` set to `password`.
5. Copy and securely store the **Client ID** and **Client Secret**.

> [!NOTE]
>
> - The token request requires **Basic authentication** using the client ID and client secret.
> - API documentation is tenant-specific and available at `https://<tenant>.mobicontrol.cloud/MobiControl/WebConsole/docs`.

## Required Permissions

SOTI MobiControl API access is tenant-specific. There is no default Base URL. The API client must have access to the following endpoints:

| Endpoint | Description |
| --- | --- |
| `/security/principal/users` | Lists user accounts in the tenant. |
| `/security/principal/users/{referenceId}/roles` | Lists security roles assigned to a user. |
| `/security/principal/roles` | Lists security roles defined in the tenant. |

Membership in the **Administrator** group satisfies all required permissions for this connector. For more detailed information on SOTI MobiControl API authentication, refer to the tenant-specific [API documentation](<https://%3Cyour tenant%3E.mobicontrol.cloud/MobiControl/WebConsole/docs>).

> [!NOTE]
>
> The linked document is not maintained by SailPoint and is subject to change without notice.

# 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 SOTI MobiControl connector uses the following default correlation and object configurations.

## 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 ID

SailPoint requires that certain attributes remain in your configuration. These attributes are referred to as *account IDs*.

> [!CAUTION]
>
> Changing the attribute marked as the account ID after aggregating accounts can result in duplicate accounts being created. To avoid this, either reset the accounts on this source before editing the account ID attribute or edit the account ID attribute before aggregating accounts.
>
> To resolve issues caused by changing account IDs, reconfigure them to their default values.

The following table lists the default account IDs for this connector:

| Account ID | Schema Object Type |
| --- | --- |
| referenceId | Account |

### Default Account Attributes

The SOTI MobiControl 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 |
| --- | --- |
| referenceId | Unique Account ID |
| name | Username of the user account |
| displayName | Display name of the user |
| emailAddress | Email address of the user |
| userKind | Type of user account (for example, local or SSO) |
| roles | Security roles assigned to the user, multi-valued group attribute |
| isEulaAccepted | Indicates whether the user has accepted the end-user license agreement |
| isAccountLocked | Indicates whether the user account is locked |
| lastPasswordChangeDate | Date the user last changed their password |
| ssoConnectionId | Identifier of the SSO connection for SSO users |
| externalId | External identifier for the user from an identity provider |
| domainName | Domain name associated with the user account |
| isHiddenUser | Indicates whether the user is a hidden system account |

## 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.

### Default Group Attributes

The SOTI MobiControl connector also supports groups. The following attributes must be configured on the managed system and in the SailPoint source schema to manage groups.

| Attribute Name | Description |
| --- | --- |
| name | Display name of the security role, used as the entitlement identity attribute |
| referenceId | Unique identifier of the security role |