On 30 Apr 2015, at 13:14, Michael Ströder <michael@stroeder.com> wrote:
Alan DeKok wrote:
On Apr 30, 2015, at 10:43 AM, Ben Humpert <ben@an3k.de> wrote:
in the schema file the entry for require message authenticator is listed as
olcAttributeTypes: ( 1.3.6.1.4.1.11344.1.100.2.6 NAME 'radiusClientRequireMa' SINGLE-VALUE DESC 'Require Message Authenticator' EQUALITY booleanMatch SYNTAX '1.3.6.1.4.1.1466.115.121.1.7' )
thus one has to enter TRUE or FALSE in LDAP - everything else (I tried it with true, Yes, yes, YES and 1) throws an LDAP error. But now, with TRUE FR won't start anymore. Below is the debug log
I've pushed a fix to v3.0.x. It will now allow true / false for booleans. ^^^^^^^^^^^^ Just in case: Please note that LDAP syntax Boolean requires upper-case TRUE / FALSE.
I saw LDAP client and server implementations which do not care about that leading to interop problems.
The comparison will be case insensitive Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS development team FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2