Re: Using ldap_xlat in unlang with Chars not allowed in an ldap search

2012-10-01 Thread Daniel Finger
Am 20.09.2012 18:28, schrieb Phil Mayers: > If you edit rlm_ldap.c around line 1231, and change: >if (!radius_xlat(url, sizeof(url), fmt, request, func)) > ...to: >if (!radius_xlat(url, sizeof(url), fmt, request, ldap_escape_func)) > ...this should work. I'll submit a one-liner. I just up

Re: Using ldap_xlat in unlang with Chars not allowed in an ldap search

2012-09-20 Thread Phil Mayers
On 29/08/12 17:42, Phil Mayers wrote: There's no easy way to do this with the built-in LDAP code. When the "xlat" is called, it's called with one big string i.e. the un-escaped value is already inside the string, and can't be escaped. Actually, following this up: I'm wrong here, due to misunde

Re: Using ldap_xlat in unlang with Chars not allowed in an ldap search

2012-08-29 Thread Phil Mayers
On 29/08/12 16:00, Daniel Finger wrote: If I have searched correctly it should work if I rewrite the Attribute with \28 for ( and \29 for ) (as ascii string, not escaped :-)) Shouldn't that be %28 and %29? Relevant docs here are RFC 4516 section 2.1, which references RFC 3986 section 2.1.

Using ldap_xlat in unlang with Chars not allowed in an ldap search

2012-08-29 Thread Daniel Finger
Hi! I have a Problem using the ldap Module to search in the ldap Tree for a specific Attribute Containing a (. I am using FreeRadius (2.1.12) for 802.1X Authentification (EAP-TLS) which is working fine. After successful EAP Authentication, I want to check if the User has an Entry in the LDAP: Du