Re: [REPOSTED FROM DEV]Issue related to TLSv3 in the LDAP API

2021-07-05 Thread Emmanuel Lécharny
We are looking at the TLSV1.3 on MINA side with Jonathan Valière. On 05/07/2021 14:13, Shawn McKinney wrote: On Jul 4, 2021, at 1:16 PM, Stefan Seelmann wrote: Oh sorry, my question regarding ApacheDS didn't make sense because in ApacheDS only TLSv1.2 is enabled so the negotiation chose

Re: [REPOSTED FROM DEV]Issue related to TLSv3 in the LDAP API

2021-07-05 Thread Shawn McKinney
> On Jul 4, 2021, at 1:16 PM, Stefan Seelmann wrote: > > Oh sorry, my question regarding ApacheDS didn't make sense because in > ApacheDS only TLSv1.2 is enabled so the negotiation chose 1.2 event if > 1.3 is enabled in the API. No worries. I needed to test LDAPS on ApacheDS anyway as it has

Re: [REPOSTED FROM DEV]Issue related to TLSv3 in the LDAP API

2021-07-04 Thread Stefan Seelmann
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

Re: [REPOSTED FROM DEV]Issue related to TLSv3 in the LDAP API

2021-07-04 Thread Shawn McKinney
> 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

Re: [REPOSTED FROM DEV]Issue related to TLSv3 in the LDAP API

2021-07-04 Thread Shawn McKinney
> 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

Re: [REPOSTED FROM DEV]Issue related to TLSv3 in the LDAP API

2021-07-04 Thread Shawn McKinney
> 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

Re: [REPOSTED FROM DEV]Issue related to TLSv3 in the LDAP API

2021-07-04 Thread Stefan Seelmann
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

Re: [REPOSTED FROM DEV]Issue related to TLSv3 in the LDAP API

2021-07-03 Thread Shawn McKinney
> On Jul 3, 2021, at 2:10 PM, Stefan Seelmann wrote: > > I added TLSv1.3 to the default protocols in [1]. There is an open issue > for Mina [2] that describes timeouts when using v1.3, please see my > comment there. When used in Studio I didn't encounter any issue in tests > against OpenLDAP

Re: [REPOSTED FROM DEV]Issue related to TLSv3 in the LDAP API

2021-07-03 Thread Stefan Seelmann
Hi Shawn, I added TLSv1.3 to the default protocols in [1]. There is an open issue for Mina [2] that describes timeouts when using v1.3, please see my comment there. When used in Studio I didn't encounter any issue in tests against OpenLDAP or 389ds, only when using it in ApacheDS, so I assumed