API Authentication
Applies toBYOC
1 min read
Automation accounts and scripts that call the Ververica API authenticate differently depending on your SSO protocol.
- OIDC: automation accounts get an access token directly from your identity provider and use it to call the Ververica API. You don't need a separate Ververica-issued token.
- SAML: generate an access token from the Ververica Console, or through the Ververica API, and use that token for automation. SAML doesn't support direct token issuance from your identity provider.
CLI Sign-In
CLI sign-in isn't supported for Ververica Cloud SSO in Public Preview or General Availability. This scope might change in a future release.
Was this helpful?