Postgresql servers can be configured to force a client to connect via ssl. Kong should allow for ssl connections to postgres in its config, as is available for cassandra. This is especially important given all the secrets that are stored in the database in plain text (e.g. jwt secrets).
For reference: https://www.postgresql.org/docs/9.1/static/ssl-tcp.html
We've been waiting on https://github.com/leafo/pgmoon/pull/24 for that. At that point we might consider using a fork of pgmoon with this patch for Kong.
This is the blocker for Kong with Postgres on Heroku, because Heroku Postgres requires SSL: https://github.com/heroku/heroku-buildpack-kong/issues/7
I'm selfishly in support of forking pgmoon to get this fix @thibaultCha
Alright, we just created a temporary fork at Mashape/pgmoon and we will include Postgres SSL connections in the upcoming 0.9 release (this month).
Has been implemented (to be released in the upcoming 0.9 version this month).
Thanks! I've been on vacation but I will take a look this week.
Most helpful comment
This is the blocker for Kong with Postgres on Heroku, because Heroku Postgres requires SSL: https://github.com/heroku/heroku-buildpack-kong/issues/7
I'm selfishly in support of forking pgmoon to get this fix @thibaultCha