-
Notifications
You must be signed in to change notification settings - Fork 21
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
Support for SSL #71
Labels
Comments
12 tasks
sebastianswms
added a commit
to sebastianswms/target-postgres
that referenced
this issue
May 18, 2023
visch
added a commit
that referenced
this issue
Jun 23, 2023
Two types of SSL are supported: - Checking the server's certificate against a certificate authority using `ssl_enable`, for verifying the server's identity to the client. - Passing a client certificate and private key to the server using `ssl_client_certificate_enable`, for verifying the client's identity to the server. Each can be configured independently of the other. Using either or both precludes the use of `sqlalchemy_url`. Closes #71. --------- Co-authored-by: Derek Visch <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is technically already supported via the sqlalchemy_url configuration. But we should add config option(s) for SSL as well so you don't have to use
sqlalchemy_url
to support this.Also as a part of this we should note in the
sqlalchemy_url
anddialect+driver
that these settings are not safe to use as they can change significantly in the future, they should be used in combination with creating a ticket going over why you had to use thesqlalchemy_url
and could not make the original configuration settings work.The text was updated successfully, but these errors were encountered: