RE: SASL authentication

"Xu, Qiang (FXSGSC)" <[email protected]> Tue, 14 Apr 2009 18:46:34 +0800
Newsgroups gmane.comp.mozilla.devel.directory
Message-ID <D8C9BC7FFCF8154FB7141EB8DB609C172905EF856F@SGPAPHQ-EXSCC01.dc01.fujixerox.net>
> -----Original Message-----
> From: 
> [email protected]
>  
> [mailto:[email protected]
> illa.org] On Behalf Of Markus Moeller
> Sent: Monday, April 13, 2009 6:08 PM
> To: [email protected]
> Subject: Re: SASL authentication
> 
> sasl_secprops = (char *)"maxssf=0";
> ldap_set_option( ld, LDAP_OPT_X_SASL_SECPROPS,  (void *) 
> sasl_secprops );

Very strange. After this expression is added into the code, its behavior looks like pingpong style: 
===================================================
<apManager> (Tue Apr 14 2009 17:54:24.215) <p7800,t3078957984,aba_ldap_interface.c,1650>
     INFO>> SASL Login
<apManager> (Tue Apr 14 2009 17:54:24.382) <p7800,t3078957984,aba_ldap_interface.c,1664>
     INFO>> SASL LDAP BIND with GSSAPI: Value of ldapStatus 0
......
<apManager> (Tue Apr 14 2009 17:54:24.390) <p7800,t3078957984,aba_ldap_interface.c,1650>
     INFO>> SASL Login
<apManager> (Tue Apr 14 2009 17:54:24.395) <p7800,t3078957984,aba_ldap_interface.c,1664>
     INFO>> SASL LDAP BIND with GSSAPI: Value of ldapStatus 81
<apManager> (Tue Apr 14 2009 17:54:24.395) <p7800,t3078957984,aba_ldap_interface.c,1671>
    ERROR>> LDAP BIND: Value of ldap failure status and text 81 Can't contact LDAP server
......
<apManager> (Tue Apr 14 2009 17:54:40.943) <p7800,t3078957984,aba_ldap_interface.c,1650>
     INFO>> SASL Login
<apManager> (Tue Apr 14 2009 17:54:41.030) <p7800,t3078957984,aba_ldap_interface.c,1664>
     INFO>> SASL LDAP BIND with GSSAPI: Value of ldapStatus 0
......
<apManager> (Tue Apr 14 2009 17:54:41.038) <p7800,t3078957984,aba_ldap_interface.c,1650>
     INFO>> SASL Login
<apManager> (Tue Apr 14 2009 17:54:41.043) <p7800,t3078957984,aba_ldap_interface.c,1664>
     INFO>> SASL LDAP BIND with GSSAPI: Value of ldapStatus 81
<apManager> (Tue Apr 14 2009 17:54:41.043) <p7800,t3078957984,aba_ldap_interface.c,1671>
    ERROR>> LDAP BIND: Value of ldap failure status and text 81 Can't contact LDAP server
......
<apManager> (Tue Apr 14 2009 17:54:57.444) <p7800,t3078957984,aba_ldap_interface.c,1650>
     INFO>> SASL Login
<apManager> (Tue Apr 14 2009 17:55:00.450) <p7800,t3078957984,aba_ldap_interface.c,1664>
     INFO>> SASL LDAP BIND with GSSAPI: Value of ldapStatus 0
......
<apManager> (Tue Apr 14 2009 17:55:00.458) <p7800,t3078957984,aba_ldap_interface.c,1650>
     INFO>> SASL Login
<apManager> (Tue Apr 14 2009 17:55:00.463) <p7800,t3078957984,aba_ldap_interface.c,1664>
     INFO>> SASL LDAP BIND with GSSAPI: Value of ldapStatus 81
<apManager> (Tue Apr 14 2009 17:55:00.463) <p7800,t3078957984,aba_ldap_interface.c,1671>
    ERROR>> LDAP BIND: Value of ldap failure status and text 81 Can't contact LDAP server
===================================================
Such pattern really confuses me. After examining the code, I found nothing is wrong with the caller in apManager. I am at a loss now.

Could you give me any more suggestions, Marcus? And anyone has had the same experience before?

Thanks,
Xu Qiang