Re: ADAM Ldapsearch using Windows Domain Account
- From: "Joe Kaplan \(MVP - ADSI\)" <joseph.e.kaplan@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 30 Jun 2006 12:49:34 -0500
Oh, and by the way, if you really need to do a simple bind to ADAM using a
Windows user's credentials, you can create a bind proxy object to enable
this scenario.
Joe K.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
"Sunny Tsang" <SunnyTsang@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:11A7A463-84DD-4ACE-9AE5-845615BC8B98@xxxxxxxxxxxxxxxx
Greetings everyone, first time here posting a question. I have spent a few
days browsing the community before mustering the courage to post what
seems
to possibly be an answered question that I just haven't understood yet.
Anyways, I just installed ADAM with the purpose of using it as a directory
phonebook service. I have an ADAM user account that I provisioned that can
log in with LDP/Ldapbrowser/Ldapsearch (enabled the account, reset
password,
set unique UPN to login without having to use the DN, grant reader role on
application partition). That is working perfectly fine.
The problem I have is when I try to use a Windows Domain account from the
AD
Domain. In the reader's role of the application, I have added the Windows
account. When I try to bind with LDP, the authentication with the Windows
account succeeds. Whenever I try to use WAB, ldapbrowser, ldapsearch, I
get
the error of "Ldap simple bind error Invalid credentials".
I would appreciate any help that I can get.
.
- Prev by Date: Re: ADAM Ldapsearch using Windows Domain Account
- Next by Date: Re: Replaceing a down DC
- Previous by thread: Re: ADAM Ldapsearch using Windows Domain Account
- Next by thread: Argentina Database Crashes
- Index(es):
Relevant Pages
|
Loading