Skip to content
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

server: http requests always fallback to system tenant #120707

Merged
merged 1 commit into from
Mar 20, 2024

Conversation

dhartunian
Copy link
Collaborator

Previously, when a default tenant was configured via the cluster setting, if that tenant was unavailable, all HTTP requests would fail if they did not specify an explicit tenant.

This change allows HTTP requests to always fallback to the system tenant if the default tenant is not available, which allows for DB Console to be reached in these scenarios.

Resolves: #120084
Epic: None

Release note: None

Previously, when a default tenant was configured via the cluster
setting, if that tenant was unavailable, all HTTP requests would fail
if they did not specify an explicit tenant.

This change allows HTTP requests to always fallback to the system
tenant if the default tenant is not available, which allows for DB
Console to be reached in these scenarios.

Resolves: cockroachdb#120084
Epic: None

Release note: None
@dhartunian dhartunian requested a review from dt March 19, 2024 17:32
@dhartunian dhartunian requested review from a team as code owners March 19, 2024 17:32
@dhartunian dhartunian requested review from a team and abarganier and removed request for a team March 19, 2024 17:32
@cockroach-teamcity
Copy link
Member

This change is Reviewable

Copy link
Contributor

@abarganier abarganier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:lgtm:. I wonder, should we provide a cluster setting that can control whether or not this behavior is used? It could be a bit of an insurance policy for us, in the event that a customer with some kind of super strict security policy doesn't end up wanting this behavior. Just an idea.

Reviewable status: :shipit: complete! 1 of 0 LGTMs obtained (waiting on @dt)

@dhartunian
Copy link
Collaborator Author

TFTR. I think it's fine as-is because HTTP access to the system tenant is still fully gated behind authn/authz so our existing security policies should cover that.

bors r=abarganier

@craig
Copy link
Contributor

craig bot commented Mar 20, 2024

Build failed (retrying...):

@craig
Copy link
Contributor

craig bot commented Mar 20, 2024

Build failed (retrying...):

@craig
Copy link
Contributor

craig bot commented Mar 20, 2024

@craig craig bot merged commit 5c26990 into cockroachdb:master Mar 20, 2024
21 of 22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

dbconsole: unable to login to any tenant if default tenant is not active
4 participants