PgAdmin3, SSL certificate connections refused

Hi,

I posted the following to pgadmin-hackers several weeks ago but have not 
received any replies.  Perhaps I posted to the wrong list, and hopefully 
pgadmin-support is the right one.  Has any once else experienced the 
same issue?

Thanks,
Gabriel


On 08/03/2015 04:37 PM, "Gabriel E. Sánchez Martínez" wrote:
> Hi,
>
> I am having an issue with pgAdmin3 that may be a bug, and wanted to 
> share it with you to see what you think.  I am running pgAdmin3 1.18.1 
> on Ubuntu 14.04.  There are several server connections configured: one 
> to the local database, and three others to remote servers.  All the 
> remote servers require client certificate authentication.
>
> Right after opening pgAdmin, I can connect to any of the databases and 
> use them as expected.  If I connect to the second server (i.e. the 
> first remote one), I can use that server without issues, but I cannot 
> establish a connection to the third or fourth servers: I get an error 
> saying "SSL Error: certificate verify failed".  I can connect to the 
> local database without problems.  In order to connect to the third and 
> fourth servers, I have to restart pgAdmin.
>
> After restarting pgAdmin, I can connect to the third and fourth 
> servers in any order.  (The third and fourth servers share the same 
> root certificate server.)  I can also connect to the first (local) and 
> second (first remote) servers.  However, once I've connected to the 
> second server, no new connections to the third and fourth servers can 
> be established.  This includes clicking on a disconnected database in 
> those servers, trying to open a query editor, or connecting after 
> disconnecting.  The error dialog has the same message.
>
> The symptoms suggest that something related to the root certificate is 
> being stored by pgAdmin once a connection is established.  It is 
> strange that the order of the servers seems to matter.  Possibly the 
> CA certificate of the first server is the one that blocks connections 
> to servers requiring SSL appearing later on the list if they use a 
> different CA certificate, but that has yet to be verified.
>
> Any ideas?
>
> Thanks and regards,
> Gabriel
>