-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use godap without LDAP credentials? #10
Comments
Hi mate, I haven't seen this scenario yet - in AD it seems to work with the method mentioned in the README. Can you provide some details on what type of LDAP server you're trying to connect to so I can try to replicate it? |
Thanks. I've actually got very little info on the LDAP server itself and the version, but it appears to be OpenLDAP. Here's some info, but it's very sparse: $ ldapsearch -x -h m1 -s base -b "" "objectClass=*"
# extended LDIF
#
# LDAPv3
# base <> with scope baseObject
# filter: objectClass=*
# requesting: ALL
#
#
dn:
objectClass: top
objectClass: OpenLDAProotDSE
# search result
search: 2
result: 0 Success
# numResponses: 2
# numEntries: 1 This is on a Rocky 8 Linux HPC environment. |
I managed to reproduce the issue here. The thing is, I used to think disallowing empty passwords was a limitation of the I just found out they have a specific method for that (UnauthenticatedBind) and it seems to work fine with AD / OpenLDAP. Can you please try the latest commit? |
Beautiful - it works. Thanks. (I leave it to you to close this issue) |
Hello, first-time user here. Is it possible to run
godap
as a non-privileged user without LDAP credentials? I can query the LDAP server usingldapsearch
. However, trying withgodap
, I get:$ ./godap myserver 2024/07/25 22:03:37 LDAP Result Code 206 "Empty password not allowed by the client": ldap: empty password not allowed by the client
Looking at https://github.com/Macmod/godap?tab=readme-ov-file#usage, I also tried:
$ godap myserver -p anything 2024/07/25 22:07:27 LDAP Result Code 49 "Invalid Credentials":
and
The above is with:
The text was updated successfully, but these errors were encountered: