Add docs for rpk OIDC (OAUTHBEARER) client authentication#1696
Add docs for rpk OIDC (OAUTHBEARER) client authentication#1696david-yu wants to merge 6 commits into
Conversation
rpk added OAUTHBEARER SASL mechanism support in v26.1.7 (also backported to v25.3.x and v25.2.x), letting users authenticate the Kafka, Admin, and Schema Registry clients with an OIDC access token. The existing OIDC section in the authentication guide only covered enabling OAUTHBEARER on the broker; this adds the matching client-side how-to and updates the rpk -X reference so OAUTHBEARER appears as an acceptable sasl.mechanism value. Ref: redpanda-data/redpanda#30169 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
✅ Deploy Preview for redpanda-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Important Review skippedAuto incremental reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
📝 WalkthroughWalkthroughThis PR updates documentation to support OIDC/OAUTHBEARER SASL authentication with rpk. It adds a comprehensive end-to-end setup guide in the authentication documentation covering rpk version requirements, cluster configuration, token passing syntax with the Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@modules/manage/partials/authentication.adoc`:
- Line 1140: The sentence currently claims that enabling OIDC on a Kafka
listener lets rpk authenticate to the Kafka API, Admin API, and Schema Registry
via OIDC; narrow or clarify this: update the sentence to state that enabling
OIDC on a Kafka listener enables rpk OAUTHBEARER authentication to the Kafka API
only, and either add a separate sentence or a cross-reference that describes the
additional/explicit OIDC requirements for the HTTP-based Admin API and Schema
Registry (e.g., different listener or token audience/configuration), mentioning
the terms rpk, OAUTHBEARER, OIDC, Kafka API, Admin API, and Schema Registry so
readers can find the relevant sections.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 52c47a34-f7d2-4366-9089-d25d7dc854e0
📒 Files selected for processing (2)
modules/manage/partials/authentication.adocmodules/reference/pages/rpk/rpk-x-options.adoc
Remove the paragraph showing -X sasl.mechanism / -X pass equivalents. The --sasl-mechanism / --password form earlier in the section plus the rpk profile example below it cover the relevant ways to pass the token. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
The previous <<oidc,...>> xrefs jumped to the top of the OAUTHBEARER section instead of the OIDC credentials flow and access token validation subsection they reference. Use the auto-generated oidc-credentials-flow-and-access-token-validation anchor so the link lands at the validated-claims content. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
kbatuigas
left a comment
There was a problem hiding this comment.
One thing before I approve, does this need to go in https://deploy-preview-1696--redpanda-docs-preview.netlify.app/current/get-started/release-notes/redpanda/? If so, we could probably add a new entry after Schema Registry contexts
| ---- | ||
| export OIDC_TOKEN="<access-token>" | ||
|
|
||
| rpk topic list \ |
There was a problem hiding this comment.
Could we update this example so that it also uses rpk -X, since we do say that these flags are deprecated?
Co-authored-by: Kat Batuigas <36839689+kbatuigas@users.noreply.github.com>
Summary
rpkaddedOAUTHBEARERSASL mechanism support in v26.1.7 (also v25.3.x and v25.2.x) for the Kafka API, Admin API, and Schema Registry clients.manage:security/authentication.adoconly covered the broker-side configuration (enablingOAUTHBEARER, settingoidc_discovery_url, etc.) but never showed how a user actually connects withrpk. SCRAM has a "Connect to Redpanda" subsection; this PR adds the parallel one for OIDC.reference:rpk/rpk-x-options.adocsoOAUTHBEARERappears as an acceptablesasl.mechanismvalue, with a note about passing the token viapass(raw ortoken:<TOKEN>).Source feature PR: redpanda-data/redpanda#30169 (merged 2026-04-22, released in 26.1.7).
Live link: https://deploy-preview-1696--redpanda-docs-preview.netlify.app/current/manage/security/authentication/#oidc-rpk
Changes
modules/manage/partials/authentication.adoc— new[[oidc-rpk]]subsection inside==== OAUTHBEARER (OIDC)covering prerequisites, the--sasl-mechanism OAUTHBEARER+--password "token:..."invocation, the-Xform, anrpk profile createexample, and troubleshooting that cross-links back to the existing credentials-flow section.modules/reference/pages/rpk/rpk-x-options.adoc— addsOAUTHBEARERto Acceptable values forsasl.mechanismand a one-paragraph note pointing to the new how-to.No new pages, no nav changes.
Test plan
[[oidc-rpk]]anchor resolves from therpk -Xreference xref.<<oidc, OIDC credentials flow and access token validation>>resolves.🤖 Generated with Claude Code