Message-ID: <gh-pgjdbc-pgjdbc-3349-c2862672148@github.com>
From: "kaushalaroraharman (@kaushalaroraharman)" <noreply+kaushalaroraharman@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Thu, 08 May 2025 11:13:44 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
In-Reply-To: <gh-pgjdbc-pgjdbc-3349@github.com>
References: <gh-pgjdbc-pgjdbc-3349@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: kaushalaroraharman
X-GitHub-Comment-Id: 2862672148
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3349
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3349#issuecomment-2862672148
Content-Type: text/plain; charset=utf-8

@davecramer A brief of the issue is that even with an expired certificate, client is able to connect to Postgres. The expectation is that with an expired certificate, connection should be refused.

Please go through https://github.com/pgjdbc/pgjdbc/issues/3349#issuecomment-2320206340, the previous comments and description for details on the issue.