# SailPoint iMeet Central Connector Documentation

> iMeet Central Connector Documentation

# Documentation

# Connecting SailPoint and iMeet Central

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. Enter the `client_id` from the downloaded JSON as **Client ID**.
2. Enter the workspace `id` from the API Explorer as **Workspace ID**.
3. Paste the contents of the encrypted PEM file, including the BEGIN and END lines, as **Private Key**.
4. Enter the passphrase you used with `openssl pkcs8` as **Private Key Password**.
5. Leave **Client Secret** blank.
6. Enter the `client_id` from the downloaded JSON as **JWT Issuer**.
7. Enter the `client_id` from the downloaded JSON as **JWT Subject**.
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 iMeet Central

iMeet Central (formerly Central Desktop) is a collaboration platform for projects, files, discussions, and tasks. The company account is the tenant. Work happens in workspaces under that company. This document covers how to configure a new direct connection between SailPoint and iMeet Central for Quick Compliance. 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 iMeet Central connector supports the following:

### Account Management

- Aggregate Users

> [!NOTE]
>
> This connector is read-only. It supports test connection and account aggregation for Quick Compliance. Provisioning, de-provisioning, and write operations are not supported. Workspace permissions are captured on the account through the `workspacePermissions` attribute during account aggregation. Separate entitlement aggregation is not required.

> [!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.

## Prerequisites

Before you configure the iMeet Central connector, ensure the following requirements are met:

1. Sign in to [iMeet Central](<https://app.imeetcentral.com/signup?demo&amp;sr=imeet_central_site>).
2. Select the gear icon in the top navigation, then select **Company Setup**.
3. Open the **Advanced** tab, then select the **API** link.
4. In the **Act as** dropdown list, select the user the client key authenticates as. The access token inherits this user's visibility. Select an account that is a member of the workspace.
5. Select **Create New Client Key**. The browser downloads a JSON file named `<companyName>-<client_id>.json` that contains `client_id` and `private_key`.
6. Copy the `client_id`. Use the same value for **Client ID**, **JWT Issuer**, and **JWT Subject**.
7. Convert the private key to PEM. The `private_key` value in the JSON is a single line with `\n` escape sequences. Expand it into a multi-line PEM before SailPoint can use it:

   1. Open the downloaded JSON file in a text editor such as Notepad (Windows) or TextEdit (Mac).
   2. Find the `"private_key"` value. Copy everything between the quotation marks. Do not copy the quotation marks.
   3. Open a new blank document and paste the value.
   4. Wherever you see `\n`, delete those two characters and press Enter so the next text starts on a new line.
8. Confirm the file looks like this:

   ```text
   -----BEGIN RSA PRIVATE KEY-----
   MIIE...
   -----END RSA PRIVATE KEY-----
   ```

   The first line must be `-----BEGIN RSA PRIVATE KEY-----` and the last line must be `-----END RSA PRIVATE KEY-----`. There should be no `\n` left in the file, and no quotation marks.
9. Save the file with a name that ends in `.pem`. For example: `imeet_private_key.pem`.
10. Encrypt the PEM and set the Private Key Password. Open a terminal (macOS/Linux) or Command Prompt / PowerShell (Windows, with OpenSSL installed) in the folder where you saved the file, then run:

    ```text
    openssl pkcs8 -topk8 -v2 aes-256-cbc -in <your-pem-file-name>.pem -out <your-encrypted-file-name>.pem
    ```
11. Replace `<your-pem-file-name>` with the file you saved, and `<your-encrypted-file-name>` with the name you want for the encrypted key. OpenSSL prompts for an encryption passphrase twice. Choose a password and remember it. That passphrase is the value for **Private Key Password**.
12. Open the encrypted file named in `-out` (it starts with `-----BEGIN ENCRYPTED PRIVATE KEY-----`). Copy the full contents, including the BEGIN and END lines, and paste that into **Private Key**. Enter the same passphrase in **Private Key Password**.
13. Retrieve the **Workspace ID**:

    1. Return to **Company Setup \> Advanced \> API**.
    2. Select **Open API Explorer**.
    3. In the explorer, expand the workspaces dropdown list and select **GET /workspaces**.
    4. Execute the request. The response returns an `items` array. Each entry contains the workspace `id` and its name.
    5. Copy the `id` of the workspace whose users you want to aggregate. For example, `WzIxLDgwMjMwNl0`.

    The connector aggregates the members of that single workspace.
14. Record the following values for connector configuration:

    - **Client ID**
    - **Workspace ID**
    - **Private Key** (PEM)
    - **Private Key Password** (the passphrase entered in the `openssl pkcs8` command)
    - **JWT Issuer**
    - **JWT Subject**

For more information about iMeet Central API authentication, refer to the [iMeet Central API documentation](<https://apidocs.imeetcentral.com/>). For detailed endpoint information, go to **Company Setup \> Advanced \> Open API Explorer**.

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

## Required Permissions

The user selected in the **Act as** dropdown list determines what the token can read. That user must:

- Be an internal member of the company.
- Be a member of the workspace configured on the source with permission to view its member list. A workspace or company administrator is recommended.

# 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 iMeet Central 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 |
| --- | --- |
| id | Account |

### Default Account Attributes

The iMeet Central 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 identifier for the user account |
| email | Primary email address of the user, used for platform communications and login |
| username | Unique login identifier for the user across all instances |
| fullName | Full name of the user |
| resourceUri | Relative API path of the user resource |
| resourceType | Resource type reported by for the account |
| permalink | Direct link to the user profile |
| createdOn | Date and time the user was created |
| lastModifiedOn | Date and time the user was last modified |
| address1 | First line of the user address |
| address2 | Second line of the user address |
| city | City of the user address |
| state | State of the user address |
| zipcode | Postal code of the user address |
| country | Country of the user address |
| customFields | Custom field values configured for the user |
| workspacePermissions | Permissions held by the user in the configured workspace |