Skip to content

Conversation

@fulghum
Copy link
Contributor

@fulghum fulghum commented Nov 10, 2025

Extends authentication handlers to validate additional connection properties (e.g. SSL, X509 client cert, cert issuer, cert subject) when additional connection constraints have been configured for a user.

Note: tests for this functionality are in dolthub/dolt#10067

Related to dolthub/dolt#10008

Copy link
Member

@zachmu zachmu left a comment

Choose a reason for hiding this comment

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

LGTM!

if !conn.TLSEnabled() {
return newAccessDeniedError(userEntry.User)
}
if userEntry.SslCipher != "" {
Copy link
Member

Choose a reason for hiding this comment

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

Are these cases supposed to fall through like they do? i.e. is it meaningful / possible to set more than one?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

correct – you can set an SSL cipher constraint, as well as a cert subject and cert issuer constraint, so we only exit with an error if we detect one of the constraints isn't met, and fall through to check the other constraints.

@fulghum fulghum merged commit 16344ed into main Nov 14, 2025
8 checks passed
@fulghum fulghum deleted the fulghum/mutual_tls branch November 14, 2025 21:41
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.

3 participants