> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-cloud-posture-management/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/gotomeeting.md).

# GoToMeeting

Use GoToMeeting data with Cortex Cloud.

The capabilities and sub-capabilities listed for this connector are available with any active Cortex XSIAM or Cortex Cloud Posture Security license.

This connector includes the following capabilities and sub-capabilities (if applicable):

* **SaaS Posture Configuration Monitoring:** Detect, monitor and alert on settings of your SaaS application.
  * **saas-posture-config-remediation:** Help remediate the misconfigured security settings of your SaaS application.

### How to configure the GoToMeeting connector

Cortex Cloud supports GoTo organizations with at least one account licensed for GoToMeeting. Accounts without a GoToMeeting entitlement are skipped during the scan; if no account in the organization is licensed, the scan fails.

GoToMeeting uses a server-to-server Personal Access Token (PAT) exchange. There is no browser consent screen and no redirect URI to configure in Cortex Cloud. Cortex Cloud Base64-encodes the Client ID and Client Secret, sends them as a Basic Authorization header, and exchanges the PAT for short-lived access tokens, refreshing them automatically.

To access GoToMeeting, Cortex Cloud requires the following information, which you will specify during the connection process.

* **Client ID:** The unique identifier for your GoTo OAuth client application, generated in the GoTo Developer Center.
* **Client Secret:** The secret key for your GoTo OAuth client application. Cortex Cloud uses the Client ID and Client Secret to authenticate token exchange requests.

> **Important:** The Client Secret is displayed only once, at the time the app is created. If you navigate away without copying it, you must regenerate the secret and update the Cortex Cloud instance.

* **Personal Access Token (PAT):** A long-lived token generated from the GoTo Developer Tools. The PAT inherits the permissions of the user who creates it. Use a GoTo Admin (Super Admin or Account Admin) account — a non-admin PAT will authenticate but return HTTP 403 on admin endpoints.

> **Important:** The Personal Access Token is displayed only once, at the time of creation. If you navigate away without copying it, you must regenerate the token and update the Cortex Cloud instance.

Perform the following procedures in the order that they appear below.

#### Task 1: Create a GoTo OAuth Client

1. Navigate to the [GoTo Developer Center](https://developer.goto.com/) and sign in with your GoTo administrator account.
2. Open **OAuth Clients** from the top navigation.
3. Click **+ Add Client**.
4. Complete the application form:

   * **App name:** for example, `Cortex_GoToMeeting_Integration`

   * **Description:** for example, `Palo Alto Networks Cortex SSPM posture monitoring`

   * **Redirect URI:** Enter any valid HTTPS URL you control, for example `https://localhost/oauth/callback`.

   * **Scopes:** Select **Get user information** from Profile and **Manage users across GoTo products** from Admin Center.

   > The Cortex GoToMeeting connector never performs a browser redirect. If the portal marks the Redirect URI field as mandatory, enter any valid HTTPS URL — it will not be used by Cortex Cloud.
5. Copy the **Client ID** and **Client Secret** and store them securely.

   > Do not continue to the next step unless you have copied both values. You must provide them to Cortex Cloud during the onboarding process.
6. Click **Create**.

#### Task 2: Enable the Personal Access Token Grant Flow

1. In the GoTo Developer Center, navigate to **OAuth Clients**.
2. Click the **Edit** (pencil) icon next to the client you created in Task 1.
3. Select **Grant types** from the left menu.
4. Toggle **Personal Access Token** to enabled.
5. Confirm that the enabled scopes on the OAuth client match the scopes you will assign to your PAT.
6. Click **Save**.

#### Task 3: Generate a Personal Access Token

1. In the GoTo Developer Center, click the **Profile** icon in the top-right corner and select **Developer Tools**.
2. Click **Create Token**.
3. Complete the form:
   * **Token Name:** for example, `Cortex_GoToMeeting_PAT`
   * **Scopes:** Select **Get user information** from Profile and **Manage users across GoTo products** from Admin Center.
4. Copy the generated **Personal Access Token** and store it securely.

   > Do not continue to the next step unless you have copied the token. It is displayed only once and cannot be retrieved after you navigate away from this page. You must provide this value to Cortex Cloud during the onboarding process.
5. Click **Done**.

#### Task 4: Connect GoToMeeting to Cortex Cloud

1. In Cortex Cloud, navigate to **Settings** → **Data Sources & Integrations**.
2. Click **+ Add new**.
3. In the **Add Data Source** page, search for GoToMeeting.
4. Under **Recommended**, hover over the new GoToMeeting integration and click **Add Instance** to launch the configuration wizard.
5. Under the **Capabilities** tab, enter a name for your application.
6. Select **Security Posture** under **Default Capabilities**. Click **Next**.
7. Under the **Connection** tab, enter the **Client ID**, **Client Secret**, and **Personal Access Token** details.
8. Under the **Configuration** tab, select a **Sync Interval**. Choose a meaningful **Tag** to distinguish between various applications in different environments.
9. A confirmation message shows that GoToMeeting is successfully connected. Confirm the **Summary** details and click **Save instance**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-cloud-posture-management/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/gotomeeting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
