On 7/4/21 8:03 PM, Shawn McKinney wrote:
>
>> On Jul 4, 2021, at 9:12 AM, Shawn McKinney wrote:
>>
>> I don’t think it’s server dependent as I’ve noticed the TLS connection and
>> binds are successful with OpenLDAP before the timeout in the API.
>>
>
> Should know by now not to ‘think’ and
> On Jul 4, 2021, at 9:12 AM, Shawn McKinney wrote:
>
> I don’t think it’s server dependent as I’ve noticed the TLS connection and
> binds are successful with OpenLDAP before the timeout in the API.
>
Should know by now not to ‘think’ and just test. Don’t know how many times
I’ve been
> On Jul 4, 2021, at 9:12 AM, Shawn McKinney wrote:
>
> I don’t think it’s server dependent as I’ve noticed the TLS connection and
> binds are successful with OpenLDAP before the timeout in the API.
Stefan,
I’ve got 2.0.6 running on a linode VM along with OpenLDAP using LDAPS.
I can make
> On Jul 4, 2021, at 8:08 AM, Stefan Seelmann wrote:
>
> On 7/3/21 7:26 PM, Shawn McKinney wrote:
>> That is when TLSv1.3 was added as a default enabled protocol in the API,
>> fortress started having LDAPS connections problems.
>>
>> Specifically, connections hang during bind ops, as
Hi again,
On 7/3/21 7:26 PM, Shawn McKinney wrote:
> That is when TLSv1.3 was added as a default enabled protocol in the API,
> fortress started having LDAPS connections problems.
>
> Specifically, connections hang during bind ops, as they’re retrieved from the
> pool.
>
> Looking at the
