You are very correct the documentation on how to use LDAP with CF is not there. ITs a
joke. I am curious though, how did you get people to authenticate using the cfldap
tag and not having set up a user directory, security context then us cfauthenticate???
I am working on doing this for my site. I keep hitting the damm wall. I have a
ticket opened with allaire and they don't know anything about this. What directory
are you using. Novell, Microsoft, Netscape??? I am using Novell's Directory Service
but they(allaire) said to do things you need Netscapes (which I doubt, but oh well).
Sorry going back to your question I know that if you use the advanced security and set
up your directory and context you have the ability to tell CF to use a SSL connection
(I don't know what it does).
It seems there are very few people who are working or have worked with this. Its
almost like we need to set up a group email list just for the people for ldap related
crap........
There are a few KB articles about setting up the user directory and Security context
and what to do.
Thats about that.....
mike
>>> [EMAIL PROTECTED] 09/06/00 03:28PM >>>
Hello everyone - do we have any CFLDAP gurus out there today? I've been
using CFLDAP to do authentication of users on my website, but changes have
been made in the corporate LDAP servers that are causing me problems and
driving me nuts. Here's the situation:
In the past, I used the LDAP server at two points in time. The first was to
register a new user for accessing my site. I would feed the LDAP server the
person's internal telephone number, and it would return to me a
Distinguished Name (DN) field, along with lots of other data about the user.
I would then store that information, and add the user to the list of site
users. Later, when the user came to the site, he'd pick his name off of a
SELECT list, enter his NT password, and hit a LOGON button. At that point
I'd grab the DN from the database (that I stored during registration), and
use it as the CFLDAP username. I'd take the password the user typed in, and
use that as the CFLDAP password. Then I'd do the CFLDAP call. If it came
back, the user was authenticated. If CF threw an error (trapped via
CFERROR), then it failed.
Well, things changed on the LDAP servers. The above worked only because of
a bug in NT, which allowed a non-secure connection to bind to the server and
do the authentication. So, they moved all of the LDAP servers to LINUX. Now
I need to use a different port (636 instead of 389) for authentication, and
more importantly, I need to do the LDAP connection via an SSL connection.
Currently, everything is timing out. The log on the LDAP server shows the
CF server doing a bind, and then nothing at all after that, so it times out,
and then the CF server times out to the browser with the "high
traffic/server load, come back later" error.
How do I get CFLDAP to use an SSL connection? There is so little
documentation on CFLDAP it's pathetic. If someone can solve this dilemma
for me, I'll buy the beer in DC!
thanks everyone,
Reed
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
