[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: (ITS#9021) TLS: can't connect: TLS: hostname does not match CN in peer certificate
- To: openldap-its@OpenLDAP.org
- Subject: Re: (ITS#9021) TLS: can't connect: TLS: hostname does not match CN in peer certificate
- From: quanah@symas.com
- Date: Fri, 10 May 2019 19:58:44 +0000
- Auto-submitted: auto-generated (OpenLDAP-ITS)
--On Friday, May 10, 2019 8:52 PM +0000 darshankmistry@yahoo.com wrote:
> Full_Name: Darshankumar Mistry
> Version:
> OS:
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (2001:420:10b:1272:fc1b:1ea:d311:6cac)
>
>
> I would like to know why Open LDAP behavior was changed where we must
> have to configure FQDN name mentioned in certificate in order to work LDAP
> authentication... else TLS start failing.
OpenLDAP has worked this way since I first started using it in 2002. This
behavior is nothing new. And this is the correct behavior.
This ITS will be closed.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>