A Java / Spring Boot sample that completes the OAuth 2.0 authorization code flow against Webex, exchanges the code for tokens using the parameters WxCC expects, and exposes the result for quick API testing.
Why use this playbook
- Avoid guesswork on token shape: Webex Contact Center APIs often need a self-contained access token. The sample adds the right token-exchange parameters so you are not debugging opaque 401s before your first successful call.
- Working reference in your stack: If your team ships on Java 17 and Spring Security OAuth2, you can copy patterns (client config, redirect URI, session-backed login) instead of translating from another language or framework.
- Fast path to a testable token: After login, call
/userinfoto see claims and copy a Bearer token into Postman, curl, Webex Contact Center Flow Builder HTTP activities, or your own middleware—useful when you are validating scopes, org entitlements, or WxCC endpoints inside real contact-center flows. - Secrets stay out of source: Client ID and secret are loaded from environment variables, aligning with how you will configure staging and production apps.
What it does
- Redirects the browser to Webex for sign-in, handles the callback, and stores the session server-side.
- Performs token exchange with
self_contained_token=truewhere applicable. - Serves a small static UI after login and a
GET /userinfoJSON endpoint for inspection and tooling.
Contact center (not generic OAuth)
- Tokens from this sample are intended for Webex Contact Center scenarios:
calling WxCC REST/GraphQL APIs and supplying
Authorization: Bearerfrom Flow Builder or other automation that runs in your CC deployment. product_types: contact_centerreflects that focus: same OAuth stack as broader Webex, but scope defaults and token exchange match WxCC integration patterns from the official WxCC samples.
Preview listing
This App Hub entry was published from an open pull request. Review the change.
Support
Third-Party Tool
—
Estimated Implementation Time
2-4 hours
Categories
A Java / Spring Boot sample that completes the OAuth 2.0 authorization code flow against Webex, exchanges the code for tokens using the parameters WxCC expects, and exposes the result for quick API testing.
Why use this playbook
- Avoid guesswork on token shape: Webex Contact Center APIs often need a self-contained access token. The sample adds the right token-exchange parameters so you are not debugging opaque 401s before your first successful call.
- Working reference in your stack: If your team ships on Java 17 and Spring Security OAuth2, you can copy patterns (client config, redirect URI, session-backed login) instead of translating from another language or framework.
- Fast path to a testable token: After login, call
/userinfoto see claims and copy a Bearer token into Postman, curl, Webex Contact Center Flow Builder HTTP activities, or your own middleware—useful when you are validating scopes, org entitlements, or WxCC endpoints inside real contact-center flows. - Secrets stay out of source: Client ID and secret are loaded from environment variables, aligning with how you will configure staging and production apps.
What it does
- Redirects the browser to Webex for sign-in, handles the callback, and stores the session server-side.
- Performs token exchange with
self_contained_token=truewhere applicable. - Serves a small static UI after login and a
GET /userinfoJSON endpoint for inspection and tooling.
Contact center (not generic OAuth)
- Tokens from this sample are intended for Webex Contact Center scenarios:
calling WxCC REST/GraphQL APIs and supplying
Authorization: Bearerfrom Flow Builder or other automation that runs in your CC deployment. product_types: contact_centerreflects that focus: same OAuth stack as broader Webex, but scope defaults and token exchange match WxCC integration patterns from the official WxCC samples.
Preview listing
This App Hub entry was published from an open pull request. Review the change.
