![]() ![]() PostgreSQL has native support for using SSL connections to encrypt client/server communications for increased security. ![]() Please find below in-line comments regarding your concern :ġ :- Why is that we need not configure anything from client end when we are using OpenSSL? What needs to be done for the client authentication? ![]() Is client machine accessing the data directory of Postgres in the server machine to get the certificate and verifies it before opening the connection?Īlso, I'm pretty sure current setup does the Server authentication. Quite a contradiction, as I have used self signed certificate here.Īlso, from my client application also, I was able to connect to my DB server by adding SSLMode=Require in the connection string.īut, I'm not able to understand, how client was able to create the connection as I have not added the server certificate in the client machine's certificate store. So, I removed the parameter from the connection string and I was able to open connection. It was mentioned in the npgsql documentation that if we are using self signed certificate, we need to add Trust Server Certificate=true in the connection string.īut, using this I got the similar error stating wrong value for key. You're right, I made a typo or I got confused with the values for SSL Mode and Trust Server Certificate.īut I was able to open a connection to my DB, using the parameter SSLMode=Require. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |