Hello Quanah,

the directive I meant was updateref (which uses an URL), not updatedn, sorry for adding confussion to the thread.

As I comment in my original post:


if I add the port to the updateref directive I can reproduce the behaviour (anonymous bind vs bind with the identity configurated in the chain overlay) only by switching the updateref beetwen the url with port and without it.

On Saturday, May 6, 2017 10:05 PM, Quanah Gibson-Mount <quanah@symas.com> wrote:

--On Friday, May 05, 2017 10:27 AM +0000 mailing lists
<listas.correo@yahoo.es> wrote:

>> config to the config used in that test?
> the chain works as expected, with the identity configurated, if the port
> is not included in the updatedn.

An DN by definition wouldn't contain port information.  Can you provide a
real example of the problem and how you fixed it?



Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP: