[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [hobbit] LDAP Test
- To: <hobbit (at) hswn.dk>
- Subject: RE: [hobbit] LDAP Test
- From: "James Wade" <jkwade (at) futurefrontiers.com>
- Date: Tue, 14 Nov 2006 16:16:47 -0600
- Thread-index: AccIN1oHQ82V6rp4TZmTWNhsv2pjRwAAqV1A
I've tried this:
ldap://systemA:389/ou=my,o=test,st=tx,c=us ldaplogin=ldapuser:passwdd
Didn't work though. I got the ou, o,st,c from the ldap folks.
Yes, I want to do a real ldap lookup. The ldap folks have created
a test account for me. We had ldap hang today, so Hobbit showed
everything fine, but now one could authenticate.
Thanks for the help.
James
-----Original Message-----
From: Henrik Stoerner [mailto:henrik (at) hswn.dk]
Sent: Tuesday, November 14, 2006 3:53 PM
To: hobbit (at) hswn.dk
Subject: Re: [hobbit] LDAP Test
On Tue, Nov 14, 2006 at 12:10:27PM -0600, James Wade wrote:
> I've compiled the LDAP test in hobbit, and I'm trying
> to test the login ability. However, I'm not sure it's working.
>
> 192.168.20.1 systemA # ldaplogin=ldapuser:passwd ldap:systemA:389
What exactly are you trying to do here?
The "ldap:systemA:389" doesn't make sense. If you want just to test if
the ldap port is open, then you should just use "ldap" - nothing more.
If you want to check if the ldap server is responding to queries, then
you must provide a full URL-style LDAP query - see the bb-hosts man-page
for details about how to do that.
Since you're messing the "ldaplogin", I assume you want to perform the
"real" LDAP lookup test.
BTW, "ldaplogin" is only needed if your LDAP server requires
authentication. Most LDAP servers allow anonymous connections for simple
lookups.
Regards,
Henrik
To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe (at) hswn.dk