Re: SASL/GSSAPI problems

[<mi...@st...>]

Wido Depping wrote:
> On Wed, 3 Nov 2004 10:05:34 +0100, Hans Aschauer <han...@ep...> wrote:
>  
>>>SASL/GSSAPI authentication started
>>>Error during LDAP bind request
>>>Reason: {'info': 'SASL(0): successful result: ', 'desc': 'Local error'}
>>
>>This error is most likely due to a wrong setup of kerberos <-> LDAP, and has
>>probably nothing to do with python-ldap.
> 
> The solution for my problem was simpler than expected.

Thanks for letting us know.

> In my code I
> had "sasl_cb_value_dict = None" instead of "sasl_cb_value_dict = {}".
> After correcting this, everything worked. However it would be good if
> the developer gets a more meaningful error message than 'local error'.

Hmm, would the patch below solve this particular problem?

> Beside that, I just want to say that python-ldap is a really nice
> library and it has helped me a lot with my Luma development, altough I
> don't use its full potential :)

I look forward to luma using the full potential of python-ldap... :-)

Ciao, Michael.

Index: Lib/ldap/sasl.py
===================================================================
RCS file: /cvsroot/python-ldap/python-ldap/Lib/ldap/sasl.py,v
retrieving revision 1.11
diff -u -r1.11 sasl.py
--- Lib/ldap/sasl.py    25 Mar 2004 14:57:02 -0000      1.11
+++ Lib/ldap/sasl.py    8 Nov 2004 23:44:36 -0000
@@ -46,7 +46,7 @@
          question-answer pairs. Questions are specified by the respective
          SASL callback id's. The mech argument is a string that specifies
          the SASL mechaninsm to be uesd."""
-        self.cb_value_dict = cb_value_dict
+        self.cb_value_dict = cb_value_dict or {}
          self.mech = mech

      def callback(self,cb_id,challenge,prompt,defresult):