cli, security: add --allow-debug-user flag to enable debug user
#158963
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
Member
|
This change is |
pritesh-lahoti
approved these changes
Dec 8, 2025
Contributor
Author
|
test failure not related to the functionality. Being tracked here: #158950 |
Contributor
Author
|
TFTR! bors r=pritesh-lahoti |
craig bot
pushed a commit
that referenced
this pull request
Dec 8, 2025
158963: cli, security: add `--allow-debug-user` flag to enable debug user r=pritesh-lahoti a=souravcrl We introduce an `--allow-debug-user` flag which now enables the debug_user from access to both sql and rpc apis. fixes: None Epic CRDB-49035 Release Note(security change): We are adding a new flag `--allow-debug-user` to the cockroach start command to explicitly allow enabling the debug_user to log into the system. This flag is currently experimental and is disabled by default. When not set, authentication attempts by `debug_user` will be rejected with an error: `"certificate authentication failed for user "debug_user""` for SQL connections and `"failed to perform RPC, as debug_user login is not allowed"` for RPC connections. This flag is intended for debugging and troubleshooting purposes and should only be enabled when necessary for diagnostic operations. The debug_user should be disabled when not actively in use. Note: Certificates must include "debug_user" as one of the principals (CommonName or SubjectAlternativeName) for this functionality. The flag controls whether such certificates are accepted for both SQL client connections and RPC connections. Co-authored-by: souravcrl <sourav.sarangi@cockroachlabs.com>
Contributor
|
Build failed: |
Contributor
Author
|
bors r+ |
craig bot
pushed a commit
that referenced
this pull request
Dec 9, 2025
158963: cli, security: add `--allow-debug-user` flag to enable debug user r=souravcrl a=souravcrl We introduce an `--allow-debug-user` flag which now enables the debug_user from access to both sql and rpc apis. fixes: None Epic CRDB-49035 Release Note(security change): We are adding a new flag `--allow-debug-user` to the cockroach start command to explicitly allow enabling the debug_user to log into the system. This flag is currently experimental and is disabled by default. When not set, authentication attempts by `debug_user` will be rejected with an error: `"certificate authentication failed for user "debug_user""` for SQL connections and `"failed to perform RPC, as debug_user login is not allowed"` for RPC connections. This flag is intended for debugging and troubleshooting purposes and should only be enabled when necessary for diagnostic operations. The debug_user should be disabled when not actively in use. Note: Certificates must include "debug_user" as one of the principals (CommonName or SubjectAlternativeName) for this functionality. The flag controls whether such certificates are accepted for both SQL client connections and RPC connections. Co-authored-by: souravcrl <sourav.sarangi@cockroachlabs.com>
Contributor
Author
|
bors r- |
Contributor
|
Canceled. |
We introduce an `--allow-debug-user` flag which now enables the debug_user from access to both sql and rpc apis. fixes: None Epic CRDB-49035 Release Note(security change): We are adding a new flag `--allow-debug-user` to the cockroach start command to explicitly allow enabling the debug_user to log into the system. This flag is currently experimental and is disabled by default. When not set, authentication attempts by `debug_user` will be rejected with an error: `"certificate authentication failed for user "debug_user""` for SQL connections and `"failed to perform RPC, as debug_user login is not allowed"` for RPC connections. This flag is intended for debugging and troubleshooting purposes and should only be enabled when necessary for diagnostic operations. The debug_user should be disabled when not actively in use. Note: Certificates must include "debug_user" as one of the principals (CommonName or SubjectAlternativeName) for this functionality. The flag controls whether such certificates are accepted for both SQL client connections and RPC connections.
souravcrl
force-pushed
the
gate-debug-user
branch
from
56112a7 to
d24d543
Compare
Contributor
Author
|
bors r+ |
Contributor
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
We introduce an
--allow-debug-userflag which now enables the debug_userfrom access to both sql and rpc apis.
fixes: None
Epic CRDB-49035
Release Note(security change): We are adding a new flag
--allow-debug-userto the cockroach start command to explicitly allowenabling the debug_user to log into the system. This flag is currently
experimental and is disabled by default. When not set, authentication
attempts by
debug_userwill be rejected with an error:"certificate authentication failed for user "debug_user""for SQL connectionsand
"failed to perform RPC, as debug_user login is not allowed"for RPCconnections.
This flag is intended for debugging and troubleshooting purposes and should
only be enabled when necessary for diagnostic operations. The debug_user
should be disabled when not actively in use.
Note: Certificates must include "debug_user" as one of the principals
(CommonName or SubjectAlternativeName) for this functionality. The flag
controls whether such certificates are accepted for both SQL client
connections and RPC connections.