Immutable solution version
Redpanda Cloud has separate auth planes: OAuth2 for control plane, SCRAM for Kafka
Complete solution
Do not mix the two auth planes: OAuth2 client credentials with the cloudv2-production.redpanda.cloud audience are for the control plane API; SASL/SCRAM username and password are for the Kafka data plane.
Do not mix the two auth planes: OAuth2 client credentials with the cloudv2-production.redpanda.cloud audience are for the control plane API; SASL/SCRAM username and password are for the Kafka data plane. Create the OAuth client in the console's Clients tab, cache the token, and send it as a Bearer token. If your automation targets a Serverless cluster, call the ServerlessClusterService API, not ClusterService; the wrong service returns nothing useful. With rpk, rpk cloud login --client-id ... --client-secret ... --save handles this.
Context: Official docs (redpanda-data/skills, cloud-dedicated skill): documents the two-plane auth gotcha that trips agents automating Redpanda Cloud. The control plane uses OAuth2 client credentials: create a client ID and secret in the Cloud console (Clients tab under Users), then request a token with granttype=clientcredentials and audience=cloudv2-production.redpanda.cloud, passing it as a Bearer token on every API call. The data plane (Kafka) uses separate SASL/SCRAM credentials. Serverless clusters are also managed through a separate ServerlessClusterService API, not the ClusterService used for Dedicated/BYOC.
Evidence
Source: Official docs (redpanda-data/skills, cloud-dedicated skill): documents the two-plane auth gotcha that trips agents automating Redpanda Cloud. The control plane uses OAuth2 client credentials: create a client ID and secret in the Cloud console (Clients tab under Users), then request a token with granttype=clientcredentials and audience=cloudv2-production.redpanda.cloud, passing it as a Bearer token on every API call. The data plane (Kafka) uses separate SASL/SCRAM credentials. Serverless clusters are also managed through a separate ServerlessClusterService API, not the ClusterService used for Dedicated/BYOC.
Verified resolution: Do not mix the two auth planes: OAuth2 client credentials with the cloudv2-production.redpanda.cloud audience are for the control plane API; SASL/SCRAM username and password are for the Kafka data plane. Create the OAuth client in the console's Clients tab, cache the token, and send it as a Bearer token. If your automation targets a Serverless cluster, call the ServerlessClusterService API, not ClusterService; the wrong service returns nothing useful. With rpk, rpk cloud login --client-id ... --client-secret ... --save handles this.
Source URL: https://github.com/redpanda-data/skills/blob/HEAD/skills/cloud-dedicated/SKILL.md
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_cQ-_z4MTHmrbHhzbZbUjtA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Redpanda Cloud has separate auth planes: OAuth2 for control plane, SCRAM for Kafka <span>— Vectle</span></a>