G
Guest
We are using forms authentication in our web app and typically query our LDAP
Servers by binding to the user node in the LDAP Tree.
We usually see the following DN used as the DN for each user..
http://serverip:389/cn=login,dc=company,dc=org
*where login is their actual windows login
In Active Directory we are seeing this format...
http://server:389/cn=firstname lastname,dc=company,dc=org
*where the cn attribute is their full name not their login
When we try to bind to the directory how should we bind if don't have the
full name from the login page? (ie we'd like to ask for a standard
username/password). The users are within their own OUs and apparently not
within the general cn=Users node too. Anyhow just wondering what format of a
DN might work other than the one above to locate a user within active
directory from an ASP.NET page. Thank you so much I really appreciate it!
Christopher
Servers by binding to the user node in the LDAP Tree.
We usually see the following DN used as the DN for each user..
http://serverip:389/cn=login,dc=company,dc=org
*where login is their actual windows login
In Active Directory we are seeing this format...
http://server:389/cn=firstname lastname,dc=company,dc=org
*where the cn attribute is their full name not their login
When we try to bind to the directory how should we bind if don't have the
full name from the login page? (ie we'd like to ask for a standard
username/password). The users are within their own OUs and apparently not
within the general cn=Users node too. Anyhow just wondering what format of a
DN might work other than the one above to locate a user within active
directory from an ASP.NET page. Thank you so much I really appreciate it!
Christopher