Establish a Secure SSL Connection to PostgreSQL DB Server
Want to know how to establish a secure connection to your PostgreSQL container in Jelastic Cloud? Look no further! Read on for all the details.
Join the DZone community and get the full member experience.Join For Free
one of the most demanded challenges in the modern world of internet of things is to gain the highest level of security. that’s why today we are going to consider the process of establishing secure ssl connection to your postgresql container, hosted at jelastic cloud.
when striving to keep information in your postgresql database safe, the first thing you need to do is to encrypt all connections to it for protecting authentication credentials (usernames / passwords) and stored data from interception.
below, we’ll explore the appropriate database server adjustment, required for ssl-enabling, and certificates generation for it. then, we’ll create and add certs for client machine and, lastly, will establish secure connection to our server via pgadmin tool. so, let’s go on!
postgresql server configuration
obviously, for this tutorial we’ll use an environment with postgresql database inside — you can easily create such if you haven’t done this yet.
1. to start with, connect to your database server via jelastic ssh gate .
2. now, in order to make it work with ssl, you need to add the following three files to the /var/lib/pgsql/data server directory:
- server.key – private key.
- server.crt – server certificate.
- root.crt – trusted root certificate.
within this tutorial, we’ll briefly consider how you can generate them by yourselves.
- we won’t explain commands parameters in details here, but if you’d like to know more, just refer to the self-signed custom ssl page in our documentation or check the official openssl site for the full list of available actions
- you can also use custom ssl certificate similarly to the described below (follow the generate a custom ssl certificate section of the linked guide to get such). in this latter case, you can skip the generation instruction and jump directly to the 6th step of this instruction
so, navigate to the mentioned folder and proceed with steps below.
3. first of all, let’s create the first file — private key:
- execute the next commands:
cd /var/lib/pgsql/data openssl genrsa -des3 -out server.key 1024
during the server.key generation, you’ll be asked for a pass phrase — specify any and confirm it to finish creation.
- now, in order to work with this key further, it’s required remove the pass phrase you’ve added previously. execute the following command for this:
openssl rsa -in server.key -out server.key
re-enter pass phrase one more time for confirmation.
- set the appropriate permission and ownership rights for your private key file with the next commands:
chmod 400 server.key chown postgres.postgres server.key
4. now, you need to create server certificate based on your server.key file, e.g.:
openssl req -new -key server.key -days 3650 -out server.crt -x509 -subj '/c=us/st=california/l=paloalto/o=jelastic/cn=mysite.com/ema email@example.com'
you can also just skip the -subj parameter within the command and pass all these arguments in the interactive mode within the automatically opened inquiry.
5. since we are going to sign certs by ourselves, the generated server certificate can be used as a trusted root certificate as well, so just make its copy with the appropriate name:
cp server.crt root.crt
now, as you have all three certificate files, you can proceed to postgresql database configurations, required for ssl activation and usage.
6. open the pg_hba.conf file, located in the same folder, for editing with any preferable terminal editor ( vim for example) or directly via the dashboard.
replace its default content with the following lines:
# type database user cidr-address method # "local" is for unix domain socket connections only local all all trust # ipv4 local connections: host all all 127.0.0.1/32 trust # ipv4 remote connections for authenticated users hostssl all webadmin 0.0.0.0/0 md5 clientcert=1
tip: in case you are going to work with the database not as default webadmin user, change the appropriate value within the last line of the file to the required name. note, that in this case, you’ll need to use the same user name for all the further commands (we’ll denote where this is required)
save the updated file.
7. to finish configurations, you need to apply some more changes to the postgresql.conf file.
navigate to its security and authentication section (approximately at the 80th line) and activate ssl usage itself, through uncommenting the same-named setting and changing its value to “ on ”. also, add the new ssl_ca_file parameter below:
ssl = on ssl_ca_file = 'root.crt'
don’t forget to save these changes.
8. lastly, restart your postgresql container in order to apply new settings:
sudo service postgresql restart
now, let’s create one more set of ssl certificate files for client instance, in order to support secure connection on both sides.
1. return to the terminal window with ssh connection to your postgresql server you’ve operated through during server setup (or reconnect to it) – you’ll need your server certificates for further actions.
once inside, generate a private key for client (also without a pass phrase , just as it was done in the previous section), for example within the tmp directory:
openssl genrsa -des3 -out /tmp/postgresql.key 1024 openssl rsa -in /tmp/postgresql.key -out /tmp/postgresql.key
2. next, create ssl certificate for your postgresql database user ( webadmin by default) and sign it with our trusted root.crt file on server.
openssl req -new -key /tmp/postgresql.key -out /tmp/postgresql.csr -subj '/c=us/st=california/l=paloalto/o=jelastic/cn=webadmin' openssl x509 -req -in /tmp/postgresql.csr -ca root.crt -cakey server.key -out /tmp/postgresql.crt -cacreateserial
- while commonly data for subj parameter can be changed to your personal data here, its common name (/cn=) must be equal to database user name you’ve set during the first certificate generation in server configuration file ( webadmin in our case)
- root.crt and server.key files should be located in the same folder the 2nd command is executed from; otherwise, the full path to them should be specified
3. after the files — postgresql.key , postgresql.crt , root.crt — are ready, you need to move them to to the .postgresql folder at your client machine (for that, you can use ftp add-on or just copy and paste files content).
tip: if such directory does not exist yet, create it with mkdir ~/.postgresql or similar command according to your os distribution.
also, if needed, you can set the key read permission for owner only with the chmod 0400 ~/.postgresql/postgresql.key command to achieve more security.
tip: don’t forget to remove keys from the tmp directory on your db server afterwards.
establish connection via pgadmin
eventually, after server and client configurations are done, you are ready to establish the connection. in our case, we’ll use the pgadmin 3 tool as an example, so get this application (or any other preferred one) installed beforehand.
we’ll consider the latter case — access environment settings , switch to the endpoints section and add new endpoint with the same-named button at the top pane.
2. now, when you have an access point, run your pgadmin 3 client and select the new server registration option.
in the properties tab of the opened window, specify the following data:
- name: any desired connection name (e.g. ssl-to-pgsql ).
- host: access point you’ve added in the first step (public ip address or endpoint access url without port number).
- port: use the default 5432 port number for external ip or endpoint’s public port (denoted in the same-named section of the appropriate column).
- username: database user you’ve set the ssl certificate and configurations for (i.e. webadmin by default).
- password: the corresponding user’s password (sent via email for webadmin or the one you’ve set otherwise).
the rest of the fields can be left unchanged or adjusted according to your requirements.
3. next, switch to the ssl tab and, for the same-named line, select the require option from the drop-down list.
that’s all! the required certificates will be loaded automatically during the first connection establishment, so just click ok to start managing your database via secure connection.
now you can bind your application to database (use the connect to database guide as an example) and enable ssl configurations for your project to encrypt your data while fetching/transferring. and in case you face any issues while configuring, feel free to appeal for our technical experts` assistance at stackoverflow .
so, go ahead and secure your project – just choose a cloud hosting provider within jelastic cloud union and register for free !
Published at DZone with permission of Tetiana Markova, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.