-
Notifications
You must be signed in to change notification settings - Fork 2
Respect sslmode
option
#197
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
Labels
enhancement
New feature or request
pgcompat
PostgreSQL compatibility and other details about standards-compliance
Comments
@WalBeh has a strong need for this, and he just renewed his interest in having it implemented. Thanks! |
crate-pdo includes an example setup using Docker/Podman Compose, for running CrateDB with SSL enabled. Using
|
This was referenced Feb 16, 2025
Merged
This patch implements the requested Outlook: Let us target switching to SSL by default paired with a 1.0.0 release? |
3 tasks
This was referenced Apr 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New feature or request
pgcompat
PostgreSQL compatibility and other details about standards-compliance
Status quo
PostgreSQL uses the
sslmode
client parameter to configure SSL connectivity options across the board, see 32.19.3. Protection Provided in Different Modes. CrateDB's SQLAlchemy dialect currently only uses thessl=true
query parameter.Proposal
Make it so that the CrateDB SQLAlchemy dialect is more standards-oriented, and will also accept the
sslmode
option, when applicable. Most prominently, @WalBeh asked forsslmode=require
, in order to strictly use SSL, but to turn off host name validation.This is needed to connect to https://localhost:4200/ successfully, which is apparent in K8s or other operational scenarios.
The text was updated successfully, but these errors were encountered: