RE: Active Directory LDAP and Security on Windows 2003

[Douglas.Knudsen]

i suppose this would depend on your AD admin .  I connect/bind to our AD via this code.  The trick is to use this samAccountName attribute in AD.


<!--- so an initial query to get the dn --->
<cfldap action="">         name="getldap"
        attributes="distinguishedName"
        start=" dc=ur co, dc=com"
   
  server="foo.go.com"
  port="389"
  filter="samAccountName=#form.userid#"
  maxrows="10"
  username="CN=elvis...."
        password="tiger">


<!--- rebind here --->
<cfldap action="">           name="auth"
          attributes="attrib1,attrib2"
          start="#getldap.distinguishedName#"
          scope="SUBTREE"
          server="foo.goo.com"
          port="389"
          username="#getldap.distinguishedName#"
          password="#form.pwd#">

Doug


-----Original  Doug Message-----
From: Robert Everland III [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 19, 2003 10:51 AM
To: CF-Talk
Subject: Active Directory LDAP and Security on Windows 2003

I am trying to follow the process set up by Macromedia to authenticate on an active directory through LDAP on a Windows 2003 server. Does anyone know if any security needs to be changed in order to authenticate on it? I am having issues getting a domain user to authenticate.
  _____  

---

[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

---