Which three methods are used in the Cisco Webex Teams API to handle the authentication and authorization processes? (Choose three.)

Question

Options

• AOAuth2 for integration
• BOAuth2 for bots
• CJWT tokens for guest access
• DAPI tokens for webhooks
• EOAuth2 for Webhooks
• FBearer token for personal access token

• A
  75% (12)
• C
  6% (1)
• D
  6% (1)
• F
  13% (2)

Explanation

Cisco Webex Teams uses OAuth2 as its core authentication and authorization framework across three distinct use cases: integrations (A), bots (B), and webhooks (E). Each represents a different actor in the Webex ecosystem - third-party apps acting on behalf of users, automated bot accounts, and event-driven notification systems - but all three leverage the OAuth2 grant flow to obtain scoped access tokens securely.

Why the distractors are wrong:

• C (JWT for guest access): While Webex does support JWT-based Guest Issuer tokens, this is a narrow edge-case mechanism for embedding guest users, not a primary auth/authorization method.
• D (API tokens for webhooks): Webhooks authenticate via OAuth2 (option E), not a generic "API token" - this option misnames the mechanism.
• F (Bearer token for personal access token): "Bearer token" is an HTTP transport scheme (the Authorization: Bearer ... header), not an authentication method. Personal access tokens are developer convenience tools for testing, not a formal auth category.

Memory tip: Think "OAuth2 is Omnipresent" - every official Webex integration path (integrations, bots, webhooks) uses OAuth2. If an answer choice names OAuth2 plus a real Webex actor, it's likely correct. JWT and Bearer are real terms but describe formats, not Webex auth methods.

No community discussion yet for this question.