Message-ID: <gh-pgjdbc-pgjdbc-3349-c2307035677@github.com>
From: "Shalaka1197 (@Shalaka1197)" <noreply+Shalaka1197@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Fri, 23 Aug 2024 12:54:00 +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: Shalaka1197
X-GitHub-Comment-Id: 2307035677
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-2307035677
Content-Type: text/plain; charset=utf-8

@davecramer From postgres code is there any mechanism to check certificate expiry for root.crt file and client.crt files ?
It is connecting for expired certificates as well.
Its seems to be bug from postgres side.