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

Added SSL settings for PostgreSQL #3259

Closed
wants to merge 2 commits into from
Closed

Conversation

rasmi
Copy link

@rasmi rasmi commented Jan 7, 2019

First commit fixes various spacing styles. Second commit adds sslrootcert, sslcert, and sslkey parameters to support various PostgreSQL SSL settings: https://www.postgresql.org/docs/current/libpq-ssl.html

See #2000.

@ghost ghost added the in progress label Jan 7, 2019
@rasmi rasmi mentioned this pull request Jan 7, 2019
Copy link
Member

@arikfr arikfr left a comment

Choose a reason for hiding this comment

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

Thanks, @rasmi! But as mentioned on the original issue, we do not use file paths in data source configuration[1]. Instead we should store the certificate itself (like we do for BigQuery service account JSON file for example). This ensures that the Redash server is stateless and can be scaled, if needed.

If psycopg2/libpq doesn't support accepting a certificate instead of a path, we can store it to a temporary location before usage.

[1] MySQL is currently using file paths for the same purpose, but that's legacy we need to redo.

@rasmi
Copy link
Author

rasmi commented Apr 11, 2019

Understood, thanks @arikfr. I'm going to close this!

@rasmi rasmi closed this Apr 11, 2019
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.

2 participants