AI-generated summary
Genesys Cloud OAuth clients enable applications to authenticate against the platform, make API requests, and sync entities with third-party systems through a structured configuration process. The platform supports four grant types designed for different use cases: Client Credentials for non-user applications requiring single-step authentication; Code Authorization/PKCE for server-side API requests offering two-step authentication and maximum security (recommended for new implementations); Token Implicit Grant for client-side browser and desktop applications with lower security (unavailable for new implementations after May 25, 2026); and SAML2 Bearer for single sign-on scenarios using Security Assertion Markup Language assertions.
OAuth client creation requires the OAuth > Client – Add permission, with SCIM integration requiring additional SCIM Integration role assignment. The workflow involves accessing Menu > IT and Integrations > OAuth, entering an application name and optional description, and selecting an appropriate grant type. Client Credential grant configuration requires assigning minimum required roles already present in the administrator's profile, associating roles with divisions (defaulting to Home Division), specifying allowed IP addresses using CIDR ranges, and setting token duration between 300 and 172,800 seconds. All grant types require token duration configuration within this range, with HIPAA-compliant organizations enforcing an additional 15-minute idle timeout. Authorization Code and Implicit grants require configuration of authorized redirect URIs (up to 125) and scope selection limited to minimum required permissions. A single Code Authorization or Implicit grant type functions across all regions except FedRAMP, which requires dedicated Authorization Code grant configuration.
Upon client creation, the system generates a Client Secret as a one-time viewable credential used for application authentication; this secret can be copied, viewed, or regenerated as needed. The configuration page displays metadata including creator name, creation date, modifier name, and modification date. For Genesys Cloud Embeddable Framework deployments, administrators generate a Client ID for use in the framework.js file, with token duration recommendations of 18 hours (64,800 seconds) to align with typical agent workday schedules. Additional redirect URIs may be required if dedicatedLoginWindow is enabled in framework.js.
SCIM integration configuration follows the same OAuth client creation process but specifies Client Credentials as the grant type and assigns the SCIM Integration role to the OAuth client with all relevant divisions included. Token duration for SCIM integration can extend to 38,880,000 seconds (maximum 450 days) with a default of 86,400 seconds, with extended durations requiring appropriate role permissions. Genesys Cloud documentation provides comprehensive guidance on integrations, OAuth authentication mechanisms, Embeddable Framework deployment options, SCIM identity management configuration for multiple providers (OneLogin, Microsoft Entra ID, and Okta), and authorization versus authentication concepts, supplemented by a feedback mechanism enabling users to rate article helpfulness and submit structured feedback.