--- title: Provisioning Webex with PingOne description: Provision Webex with PingOne. component: pingone page_id: pingone:integrations:p1_provisioning_connection_webex canonical_url: https://docs.pingidentity.com/pingone/integrations/p1_provisioning_connection_webex.html llms_txt: https://docs.pingidentity.com/pingone/llms.txt docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md revdate: July 8, 2026 section_ids: provisioning-capabilities: Provisioning capabilities before-you-begin: Before you begin steps: Steps validation: Validation webex-directory-attributes: Webex directory attributes limitations: Limitations --- # Provisioning Webex with PingOne Webex supports user lifecycle and access management through PingOne provisioning. By using the Webex connection in PingOne, you can provision users, groups, and memberships between Webex and PingOne. ## Provisioning capabilities The following table summarizes the inbound and outbound provisioning capabilities for each resource type: | Resource | Capability | Description | Inbound | Outbound | | ---------- | -------------- | ------------------------------------------------------------ | ------- | -------- | | User | Create | Generates a new user record in the destination. | Yes | Yes | | | Read | Retrieves or polls user attributes for synchronization. | Yes | Yes | | | Update | Modifies existing attributes, such as `first name`. | Yes | Yes | | | Delete | Deletes a user or temporarily suspends an account. | Yes | Yes | | Group | Create | Provisions a new group in the target application. | No | Yes | | | Rename | Updates the display name or identifier of an existing group. | No | Yes | | | Delete | Removes a group from the target application. | No | Yes | | Membership | Add and remove | Adds or removes users from groups. | No | Yes | ## Before you begin Make sure that you have: * A Webex account. Learn more in [Getting started with Webex](https://developer.webex.com/docs) in the Webex documentation. * The following from your Webex account: * **Client ID** * **Client Secret** * **Token Endpoint** * **Grant Type** * **Refresh Token** * Users created and assigned to a group specifically for Webex provisioning in PingOne. Learn more in [Adding a user in PingOne](../directory/p1_adduser.html) and [Managing groups](../directory/p1_managing_groups.html). ## Steps 1. Create a Webex connection: 1. In the PingOne admin console, go to **Integrations > Provisioning**. 2. Click the **Plus [icon: plus, set=fa]**icon and then click **New Connection**. 3. Click **Select** for **Identity Store**. 4. Click **Select** for the **Webex** connection, and click **Next**. 5. Enter a **Name** and **Description** for the connection. 6. Click **Next**. 7. In the **Configure Authentication** section, enter the following configurations that apply to your Webex account: * **Service URI**: Enter the base URL for the Webex API endpoint, such as `https://webexapis.com/v1`. * **Authentication Method**: Select either of the following: * **OAUTH**: Enter the following: | Field | Example | | ------------------ | ------------------------------------------------------------------------------------------------------------ | | **Client ID** | `C5692ab0958b1f3aebca1ed31161876e49a37323dac6df0cd12a181059ba86b66` | | **Client Secret** | `e457b25f5005042bc1b985decda36c8fc30765d92d81ef2ef9ad70637f976303` | | **Token Endpoint** | `https://webexapis.com/v1/access_token` | | **Grant Type** | `refresh_token` | | **Refresh Token** | `RzY3ZDNkYmUtMDAyNy00OGNiLWJmODYtMzE0ZWVjMDVhYTY0Y2IxMGZhNDMtOTY3_P0A1_ccbad3e7-d2d0-4a39-ab94-8770a15d2dbf` | * **TOKEN**: Enter the **Bearer Token**, such as `MjQ5NGYzOWEtZTkzMy00MzhlLWE0NzItNDhjNThmYTJhYzE5ZjdmMmRiNmQtYzcz_P0A1_ccbad3e7-d2d0-4a39-ab94-8770a15d2dbf`. 8. Click **Next**. 9. In the **User Actions** section, enter the following as needed: | Field | Description | | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Enable users creation** | Creates a user in the target identity store when the user is created in the source identity store. | | **Enable users updation** | Updates user attributes in the target identity store when the user is updated in the source identity store. | | **Enable users deprovision** | Deprovisions a user in the target identity store when the user is deprovisioned in the source identity store. If **Enable users deprovision** is selected, the following options appear:- **Remove Action**: To remove a user in the target identity store when the user is deleted in the source identity store, select **Delete**. - **Deprovision on rule deletion**: Deprovisions users if the associated provisioning rule is deleted. | 10. Click **Save**. 11. To enable the connection, click the toggle at the top of the details panel to the right (blue). | | | | - | ------------------------------------------------------------------------- | | | You can disable the connection by clicking the toggle to the left (gray). | 2. Create an [inbound](p1_create_provisioning_rule_inbound.html) or [outbound](p1_create_provisioning_rule_outbound.html) rule and select the existing Webex connection as the target or source. You can optionally add [attribute mappings](#webex-directory-attributes). Use the following inbound mapping examples for the Webex rule configuration: | Webex | PingOne Directory | | ----------- | ----------------- | | `emails` | `Email Address` | | `lastName` | `Family Name` | | `firstName` | `Given Name` | | `emails` | `Username` | Use the following outbound mapping examples for the Webex rule configuration: | PingOne Directory | Webex | | ----------------- | ------------- | | `Username` | `displayName` | | `Email Address` | `emails` | | `Given Name` | `firstName` | | `Manager Name` | `Manager` | | `Family Name` | `lastName` | | `ManagerID` | `Manager ID` | ## Validation * View the [sync status](p1_view_sync_status.html) to confirm users and groups are successfully provisioned to Webex and to check for errors. * Review [sync summary examples](p1_outbound_group_provisioning_sync_summary_examples.html) to help interpret your results. ## Webex directory attributes The following table lists common Webex attributes that can be mapped for user provisioning: | PingOne Attribute | Description | | ----------------- | --------------------------------------------------------------- | | `displayName` | The display name for the Webex user. | | `emails` | The user email attribute used for synchronization and matching. | | `firstName` | The user's given name. | | `lastName` | The user's family name. | | `Manager` | The manager name-value used in outbound mapping. | | `Manager ID` | The manager identifier value used in outbound mapping. | ## Limitations PingOne doesn't support enabling or disabling Webex users through provisioning.