On 12/02/2019 22:26, Christopher Schultz wrote:
> Mark,
>
> On 2/12/19 13:27, Mark Thomas wrote:
>> Try again. Prompted for certificate. Select valid cert. Connection
>> refused. Ah. the trust store again. Switch back to the OpenSSL
>> config.
>
> This is a real point of confusion for users... th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 2/12/19 13:27, Mark Thomas wrote:
> Try again. Prompted for certificate. Select valid cert. Connection
> refused. Ah. the trust store again. Switch back to the OpenSSL
> config.
This is a real point of confusion for users... the differenc
You're (both) quite right, my apologies.
(this is embarrassing)
In my defense, I've been bouncing back and forth between my personal
desktop machine (windows 10)
where I was having this issue...
and a development server, where this was working just fine.
While at lunch, it occurred to me to wonde
On 12/02/2019 17:21, John Palmer wrote:
> using the old Connector/clientAuth="true" or the new
> Connector/SSLHostConfig/ certificateVerification="REQUIRED" (tried
> lowercase and without the D) format..doesn't seem to work properly.
>
> no matter what value I use or which format... the b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
John,
On 2/12/19 12:21, John Palmer wrote:
> using the old Connector/clientAuth="true" or the new
> Connector/SSLHostConfig/
> certificateVerification="REQUIRED" (tried lowercase and without the
> D) format..doesn't seem to work properly.
>
> no m
using the old Connector/clientAuth="true" or the new
Connector/SSLHostConfig/ certificateVerification="REQUIRED" (tried
lowercase and without the D) format..doesn't seem to work properly.
no matter what value I use or which format... the behavior seems to be that
the client cert is prompt
