17 messages in net.sourceforge.lists.courier-usersRe: [courier-users] authldap against ...
FromSent OnAttachments
Arturo 'Buanzo' BusleimanOct 19, 2007 4:35 am 
Jerry AmundsonOct 19, 2007 7:20 am 
Arturo 'Buanzo' BusleimanOct 19, 2007 2:39 pm 
Larry MooreOct 19, 2007 4:31 pm 
Arturo 'Buanzo' BusleimanOct 19, 2007 5:41 pm 
Larry MooreOct 19, 2007 7:08 pm 
Arturo 'Buanzo' BusleimanOct 19, 2007 7:18 pm 
Sam VarshavchikOct 19, 2007 8:01 pm 
Arturo 'Buanzo' BusleimanOct 20, 2007 5:24 am 
Sam VarshavchikOct 20, 2007 6:02 am 
Larry MooreOct 20, 2007 3:37 pm 
Larry MooreOct 20, 2007 3:53 pm 
Arturo 'Buanzo' BusleimanOct 22, 2007 6:26 am 
Enda CronnollyOct 22, 2007 6:33 am 
Arturo 'Buanzo' BusleimanOct 22, 2007 1:18 pm 
Larry MooreOct 22, 2007 5:35 pm 
Larry MooreOct 22, 2007 5:38 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] authldap against ADS+SFU 3.5Actions...
From:Larry Moore (lmo@starwon.com.au)
Date:Oct 20, 2007 3:53:50 pm
List:net.sourceforge.lists.courier-users

Sam Varshavchik wrote:

Google search actually finds a better set of /IBM/'s documentation for the various LDAP functions, which tell me that specifying the SASL authentication mechanism as NULL gives me the default simple authentication -- which seems to work with openldap.

Pathetic. In any case, I could take a look at ldapsearch's source and try to extrapolate documentation for ldap_sasl_bind_s(). Should I?

Go ahead.

Just tried using ldapsearch and the -W and -X option with the correct password and also an incorrect one with a valid Kerberos ticket. On both occasions the lookup succeeded. Perhaps this test (OpenLDAP 2.3.24) may be a wrong approach to determine functionality but do you think the re-bind will work correctly using the DN and the Kerberos ticket already retrieved?

Larry.