Skip to content

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.

Note

To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the SaaS Release Notes 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.
  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:

    -----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:

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