Docs for JWT/OIDC authorization in v25.4 #20921
Open
+667
−15
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for cockroachdb-api-docs canceled.
|
✅ Deploy Preview for cockroachdb-interactivetutorials-docs canceled.
|
✅ Netlify Preview
To edit notification comments on pull requests, go to your Netlify project configuration. |
This commit addresses critical documentation issues in sso-sql.md where JWT authentication was incorrectly presented as requiring OIDC/DB Console configuration. JWT authentication works independently with external IdPs. Changes to sso-sql.md: - Rewrite intro to clarify JWT tokens come from external IdPs (primary method) - Position DB Console JWT generation as optional convenience feature - Add v25.4 features introduction (JWT authorization, user provisioning) - Fix prerequisites: remove incorrect OIDC requirement, clarify user provisioning - Update "Authenticate to your cluster" section to distinguish two JWT methods - Remove product scope restrictions (Enterprise license no longer required) - Remove misplaced callout about DB Console availability Changes to sso-db-console.md: - Add callout clarifying Basic/Standard clusters lack DB Console access - Link to cloud-sso-sql.md for alternative authentication on those tiers Based on evidence from: - Engineering docs (jwtauthccl package architectural independence) - Release history (JWT auth v22.2, DB Console generation v23.1) - Cloud docs (cloud-sso-sql.md explicitly mentions "external IdP") - Code analysis (no OIDC dependencies in JWT authentication) Fixes confusion where users believed JWT authentication required DB Console or OIDC configuration, when it actually works with any external IdP.
souravcrl
reviewed
Nov 3, 2025
src/current/v25.4/sso-sql.md
Outdated
| -- View all JWT-provisioned users | ||
| SELECT rolname, rolprovisionsrc | ||
| FROM pg_roles | ||
| WHERE rolprovisionsrc LIKE 'jwt_token:%'; |
There was a problem hiding this comment.
Does this work? We haven't added any new columns to the pg_roles table. The existing role options table was changed to have a new option type 'PROVISIONSRC'. with value as mentioned.
Contributor
Author
There was a problem hiding this comment.
@souravcrl Thanks - confirmed incorrect. In a new commit, I've replaced this with using SHOW ROLES. Please take a look, and if everything else in the PR looks good, please approve and I'll merge it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes DOC-13052
NEW - v25.4/jwt-authorization.md
NEW - v25.4/oidc-authorization.md
REWRITE - v25.4/sso-sql.md
Minor updates: