Hi Brad,
LDAPSend.Logon does only connect the LDAP-Server. It don't need the
username.
For LDAPSend.Bind you need 3 things:
The username, password and the ActiveDirectory Domainname.
If the username is 'alex' and the ActiveDirectory Domainname is
'company.sample.ads' then use:
LDAPSend.UserName := '[EMAIL PROTECTED]'
That's all!
Alex
Peter,
I did get the latest version if synapse to test my changes. No matter
what username I use, using the code block below, I'm always able to logon
(regardless if the username exists or not). However, I'm still never able
to bind (without using the DN as my username). At this point I'm confused
and probably don't understand some fundamental aspects of LDAP. Like I said
in a previous post, I was envisioning a user providing his/her username and
password on a web page in my app. I'd then use that username and password
to login/bind to the ldap server. I have a config file to store the server,
port, userpath, ssl info, etc. In your example below, it doesn't look like
the userpath is even used. I'm just confused at this point on how I
authenticate a user logging into my app using their ldap username/password.
Any help would be greatly appreciated.
_____
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
synalist-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/synalist-public