Which token should be used to authenticate an API integration for Cloud Manager?

Which token should be used to authenticate an API integration for Cloud Manager?

• A. JSON Web Token
• B. OAuth2 Token
• C. Web API Token
• D. Oak Login Token

Answer: (A)

JSON Web Token is used because API integrations with Cloud Manager are typically server-to-server and need a secure, non-interactive way to prove identity. A JWT is created with claims (like issuer, subject, audience, issued-at time, and expiration) and signed with a private key. This signed assertion is sent to the OAuth 2.0 token endpoint to exchange for an access token, which you then include in API requests as a bearer token. This flow supports automated scripts and CI/CD pipelines without requiring a user to log in each time. The other options don’t fit as the direct authentication method for an integration. An OAuth2 token is the result of a suitable flow after proving identity, not the initial assertion you present to establish the integration in many Cloud Manager setups. The terms Web API Token and Oak Login Token aren’t standard mechanisms for this authentication pattern.

JSON Web Token is used because API integrations with Cloud Manager are typically server-to-server and need a secure, non-interactive way to prove identity. A JWT is created with claims (like issuer, subject, audience, issued-at time, and expiration) and signed with a private key. This signed assertion is sent to the OAuth 2.0 token endpoint to exchange for an access token, which you then include in API requests as a bearer token. This flow supports automated scripts and CI/CD pipelines without requiring a user to log in each time.

The other options don’t fit as the direct authentication method for an integration. An OAuth2 token is the result of a suitable flow after proving identity, not the initial assertion you present to establish the integration in many Cloud Manager setups. The terms Web API Token and Oak Login Token aren’t standard mechanisms for this authentication pattern.