Re: (ITS#8767) Binddn issue with a comma in the DN

[clement.oudot@savoirfairelinux.com]

Le 02/11/2017 =C3=A0 07:26, clement.oudot@savoirfairelinux.com a =C3=A9cr=
it :
> Le 31/10/2017 =3DC3=3DA0 17:39, michael@stroeder.com a =3DC3=3DA9crit :
>> 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 afte=
r
>> 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 b=
e
>> 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=3D=
20
> have the error.
>
> =3D3D=3D3D slapd.conf =3D3D=3D3D
> idassert-bind bindmethod=3D3D"simple" binddn=3D3D"cn=3D3DLastname\,=3D2=
0
> Firstname,ou=3D3Dusers,dc=3D3Dexample,dc=3D3Dcom" credentials=3D3D"secr=
et" mode=3D3D=3D
> "legacy"=3D20
> flags=3D3D"non-prescriptive"
>
> =3D3D=3D3D slaptest -f slapd.conf =3D3D=3D3D
> 59faba5e invalid bind config value binddn=3D3Dcn=3D3DLastname,=3D20
> Firstname,ou=3D3Dusers,dc=3D3Dexample,dc=3D3Dcom
> 59faba5e slapd.conf: line 31: "idassert-bind <args>": unable to parse=3D=
20
> field "binddn=3D3Dcn=3D3DLastname, Firstname,ou=3D3Dusers,dc=3D3Dexampl=
e,dc=3D3Dcom=3D
> ".
> slaptest: bad configuration file!
>
>
> Seems the escaping is not taken into account.


Hello,

can someone confirm this is not a bug? In this case; how should we=20
escape the value? I tried several things, without success.



Cl=C3=A9ment.