# SailPoint GoToMeeting SaaS Connector Documentation

> GoToMeeting SaaS Connector Documentation

# Documentation

# Connecting SailPoint and GoToMeeting SaaS

To connect SailPoint with GoToMeeting, 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 **Actions**.
5. In the **Actions** dropdown list, select the setup method:

   - [**Express Setup**](<#configuring-a-source-using-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**](<#configuring-a-source-using-standard-setup>) - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup.

### Configuring a Source Using Express Setup

Express Setup minimizes the initial configuration process so you can quickly connect the application and immediately begin aggregating user account and entitlement data.

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**
   >
   > The source name must be unique. You can change these settings later in the source configuration.
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** section.
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.

### Configuring a Source Using Standard Setup

Use Standard Setup to configure the connector for full feature support.

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

Provide the information required to connect and interact with the source.

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

To configure the connection settings, complete the following:

1. Enter the **API URL** of the GoToMeeting instance. For example, `https://api.getgo.com/admin/rest`.
2. Enter the unique key associated with the company account in **Account ID**.
3. Enter the **Token URL** used to generate the access token required to authorize the instance.
4. Enter the **Client ID** and **Client Secret** for OAuth2 authentication used to generate the access token.
5. Enter the **Refresh Token** required to obtain new access tokens as needed.
6. Select **Save**.

## Aggregation Settings

For more information about aggregation, refer to [Loading Account Data](<https://documentation.sailpoint.com/saas/help/accounts/loading_data.html>).

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

1. Set the **Page Size** to limit the maximum number of results. Default: 100.
2. Select **Save**.

## Additional Settings

> [!NOTE]
>
> **Screenshot**
>
> [![Additional Settings](<https://documentation.sailpoint.com/connectors/gotomeeting/saas/help/img/additional_settings.png>)](<https://documentation.sailpoint.com/connectors/gotomeeting/saas/help/img/additional_settings.png>)

1. Select **Additional Settings** from the menu.
2. Enter the specific error to retry during provisioning in **Retryable Errors**.
3. 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 GoToMeeting SaaS

This guide is designed to give specific information about the requirements and field definitions needed to get a working instance of a GoToMeeting SaaS connector.

> [!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 SailPoint GoToMeeting SaaS connector supports the following features:

> [!NOTE]
>
> Before you can use any item above marked with an asterisk (\*), SailPoint must activate the feature for your site.

- Load and \*provision GoToMeeting Accounts
- \*Access Certifications (certification of entitlements connected to accounts)
- [Admin APIs](<https://developer.goto.com/admin/#tag/Users>) that GoToMeeting recommends
- Admin roles access management: The GoToMeeting SaaS connector supports Admin Roles usage for Access Management. You must manually add the `adminRoles` attribute that provides role based access. Refer to [Editing a Source Schema](<https://documentation.sailpoint.com/saas/help/accounts/schema.html#editing-an-account-schema>). The `adminRoles` attribute is an entitlement and it can have multiple values.
- Delete Accounts

For more information on features, refer to [Source Features](<https://community.sailpoint.com/knowledge/Identity-Security-Cloud-Source-Features>).

## Supported Managed Systems

The GoToMeeting Cloud Application as set-up in your IT environment.

## Prerequisites

- An access token has been generated using the OAuth2 flow to make API calls. For more information, refer to [How to Obtain and Use Refresh Tokens](<https://developer.goto.com/guides/Authentication/05_HOW_refreshToken/>).

#### Prerequisites for Token Generation Through OAuth API Version 2

- **New Token**: The connector requires the access token and/or the refresh token that is generated using the Client Access ID and Client Secret Key.

  The Client Access ID and Client Secret Key information is available with the OAuth Client configured with the GoToMeeting instance.

  - To create or update the OAuth Client, refer to [How to create an OAuth client](<https://developer.goto.com/guides/Get Started/02_HOW_createClient/>).
  - To generate token, refer to [How to obtain an access token](<https://developer.goto.com/guides/Authentication/03_HOW_accessToken/>).
  - To generate a refresh token, refer to [How to obtain and use refresh tokens](<https://developer.goto.com/guides/Authentication/05_HOW_refreshToken/>).

    > **Note**
    >
    > SailPoint recommends using the refresh token as it is valid for 30 days, whereas the access token is valid for only 1 hour.
- **Scope**: With the support of OAuth API V2, there is additional scope that must be added in the OAuth Client. To update the scope of the existing OAuth Client, refer to [How to create an OAuth client](<https://developer.goto.com/guides/Get Started/02_HOW_createClient/>).

## Required Permissions

The service account must have the role and permissions of an administrator.

### Admin Roles Access Management Permissions

The GoToMeeting SaaS connector supports the access using Admin Roles. The following are the admin roles that can be assigned to the user:

| User | Operation |
| --- | --- |
| SUPER\_USER | Can create other administrator or manager roles; receives all other admin roles; can modify account settings. |
| MANAGE\_USERS | Create, delete, and modify users. |
| MANAGE\_SEATS | Distribute licenses to existing users. |
| MANAGE\_SETTINGS | View and modify product specific settings for users (not account settings). |
| MANAGE\_GROUPS | Create, delete, and modify groups. |
| RUN\_REPORTS | Run reports. |

# Machine Account Attributes

## Machine Account Provisioning Attributes

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

| Attribute | Type | Generator | Description |
| --- | --- | --- | --- |
| email | string | Static | Email of the account |
| firstName | string | Static | First name of the account |
| lastName | string | Static | Last name 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 GoToMeeting SaaS connector supports provisioning, allowing you to create and manage accounts and entitlements in GoToMeeting 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

The following are the mandatory provisioning policy attributes for account creation:

| Account Attribute | Description |
| --- | --- |
| email | The email address of the user. |
| firstName | The first name of the user. |
| lastName | The last name of the user. |

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

## 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 GoToMeeting SaaS source, the default correlation mapping is:

| Account Attribute | Operation | Identity Attribute |
| --- | --- | --- |
| Email | Equals | Work Email (email) |

## 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 |
| --- | --- |
| OrganizerKey (numeric) | Account |

| Entitlement ID | Schema Object Type |
| --- | --- |
| GroupKey | Group |

### Default Account Attributes

The GoToMeeting 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 |
| --- | --- |
| OrganizerKey | A unique key associated with each organizer. |
| FirstName | The first name of the organizer. |
| LastName | The last name of the organizer. |
| Email | The email ID of the organizer. |
| Status | The status of the organizer. Active, invited or suspended. |
| GroupKey | A unique key associated with a group of which the organizer is a part of. |
| Groups | The entitlements of the organizer. |
| MaximumAttendeesAllowed | The maximum number of attendees allowed for the organizer. |

#### Admin Roles Access Management

The GoToMeeting SaaS connector supports Admin Roles usage for Access Management. Add the following attribute manually to provide role based access:

`adminRoles`: Provides role based access. This entitlement attribute can have multiple values.

> [!NOTE]
>
> For updated account-role assignment after adding the attribute in the schema, account aggregation is recommended.

## 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 GoToMeeting SaaS 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 |
| --- | --- |
| GroupName | The name of the group. |
| GroupKey | A unique key associated with the group. |
| ParentKey | The parent key of the group. |
| GroupStatus | The status of the group. |
| NumberOfOrganizers | The number of organizers in 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>).

## The API Call Rate Has Been Exceeded for the Day

This is due to a rate limit associated with the instance.

**Resolution**: Operation can be retried the next day. In the case of an increase in the rate limit, contact GoToMeeting Customer Support.