Le 31/10/2017 =C3=A0 17:39, michael@stroeder.com a =C3=A9crit :
The ITS is only for reporting bugs. This is not a bug. It's a usage question.
You should post such questions to openldap-technical mailing list after subscribing to it:
https://www.openldap.org/lists/mm/listinfo/openldap-technical
A short hint about escaping, e.g. a comma in DN string representation:
https://tools.ietf.org/html/rfc4514#section-2.4
Note that depending on your client config system more escaping might be needed because of the config syntax.
Hello Michael,
it seems to be a bug, as if I escape the comma in slapd.conf, I still=20 have the error.
=3D=3D slapd.conf =3D=3D idassert-bind bindmethod=3D"simple" binddn=3D"cn=3DLastname,=20 Firstname,ou=3Dusers,dc=3Dexample,dc=3Dcom" credentials=3D"secret" mode=3D= "legacy"=20 flags=3D"non-prescriptive"
=3D=3D slaptest -f slapd.conf =3D=3D 59faba5e invalid bind config value binddn=3Dcn=3DLastname,=20 Firstname,ou=3Dusers,dc=3Dexample,dc=3Dcom 59faba5e slapd.conf: line 31: "idassert-bind <args>": unable to parse=20 field "binddn=3Dcn=3DLastname, Firstname,ou=3Dusers,dc=3Dexample,dc=3Dcom= ". slaptest: bad configuration file!
Seems the escaping is not taken into account.
Cl=C3=A9ment.