-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ccl/jwtauthccl: allow tenants to set jwt auth settings #92406
Merged
craig
merged 1 commit into
cockroachdb:master
from
kpatron-cockroachlabs:kpatron/tenant-writable-jwt-settings
Nov 30, 2022
Merged
ccl/jwtauthccl: allow tenants to set jwt auth settings #92406
craig
merged 1 commit into
cockroachdb:master
from
kpatron-cockroachlabs:kpatron/tenant-writable-jwt-settings
Nov 30, 2022
+4
−4
Conversation
This file contains 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
9699e4f
to
b060627
Compare
knz
approved these changes
Nov 24, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
great thanks
bors r+ |
Build failed (retrying...): |
Build failed (retrying...): |
Build failed (retrying...): |
Build failed: |
bors r- |
c76f2be
to
ff83994
Compare
Previously, tenants were prevented from modifying the cluster settings that controlled jwt based auth. This prevented these customers from using external signers and made it more complicated for us to support CC serverless cluster SSO. This change makes it so that tenants can configure their JWT auth cluster settings. This paves the way for full support of cluster SSO in severless. Fixes CC-8608. Release note (enterprise change): JWT authentication cluster settings can now be modified from within tenants to better support serverless use cases.
ff83994
to
4b4d925
Compare
bors r+ |
Build succeeded: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previously, tenants were prevented from modifying the cluster settings that controlled jwt based auth. This prevented these customers from using external signers and made it more complicated for us to support CC
serverless cluster SSO.
This change makes it so that tenants can configure their JWT auth cluster settings. This paves the way for full support of cluster SSO in severless.
Release note (enterprise change): JWT authentication cluster settings can now be modified from within
tenants to better support serverless use cases.