389 v. 1.2.6 (bug) boolean value are case sensitive (eg."true" doesn't work)
Roberto Polli wrote:
> Hi all,
> Since 1.2.6 I found this bug.
> * lowercase boolean values are refused.
> ex. this won't work anymore
> syncmlEnabled: true
> I must use:
> syncmlEnabled: TRUE
> quite strange behavior:
> Let me know + Peace,
Yes, this was changed due to RFC 4517 enforcement -
http://www.ietf.org/rfc/rfc4517.txt - section 3.3.3:
The LDAP-specific encoding of a value of this syntax is
defined by the following ABNF:
Boolean = "TRUE" / "FALSE"
Which means the value must be a literal "TRUE" or "FALSE" - all upper case.
389 users mailing list