httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brad Nicholes" <>
Subject Re: svn commit: r411306 - /httpd/httpd/trunk/modules/aaa/mod_authnz_ldap.c
Date Mon, 05 Jun 2006 14:59:33 GMT
>>>> Graham Leggett <> 6/4/2006 2:42 AM >>>
>Brad Nicholes wrote:
>>> Should we define our own macro which uses LDAP_SECURITY_ERROR or
>>> more detailed logic, to keep the mainline code cleaner and support
>>> reuse in other paths
>> I thought about that and couldn't really decide if we should define
>> LDAP_SECURITY_ERROR macro in the ldap header in apr-util or not.  I
>> finally decided that if we started down that road then there are
>> probably a lot more macros and other differences between the LDAP
>> and how far should we take it.  So rather than try to redefine all
>> the missing macros and  force a dependancy on between httpd and
>> apr-util, I would just solve it in authnz_ldap.  We could certainly
>> rethink this and try to solve it in apr-util instead.
>apr_util already defines a number of macros for the purposes of 
>standardising them, particularly for the SSL/TLS stuff where every
>toolkit insisted on doing it differently, so we have already gone down

>that road.
>Standardising the macros is one thing that apr_util helps with to make

>LDAP access toolkit independent.
>The best solution IMHO is to add APU_LDAP_something to apr_util 
>depending on how the different toolkits handle LDAP_SECURITY_ERROR
>this macro mean security error?). Will have to look at the different 
>toolkits to work out what "something" should be.
>In the mean time though the patch is reasonable as is, it can be
>once apr_util is patched and another apr_util is released.

+1, I'll add a new macro to apr-util and call it
APU_LDAP_SECURITY_ERROR.  With the patch that is currently in place in
authnz_ldap, we can add the APU macros now and then remove the
authnz_ldap patch at a latter time once a new APR-Util has been
released.  I think the basic differences between the SDKs is whether the
macro exists or not.  Also from what I could see, there seemed to be a
naming difference between the Microsoft SDK and the others with the
be easily handled in the APU macro as well.


View raw message