-
Notifications
You must be signed in to change notification settings - Fork 29
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
Access to LDAP error codes in exceptions #42
Comments
Yes, that seems like a good idea. Not sure why I didn't add that initially. The spot that it needs to be added is here: Now that I look, there doesn't seem like a good way to get the normal LDAP error code in LdapTools. I can try to add something soon. As a workaround you could do:
Sorry about that :-/ |
I'm now exposing the last error code in the LdapConnectionException when possible: ldaptools/ldaptools@1943348. However, since I had to change the interface I can't really tag a minor version. If I don't make any other changes soon I'll just tag another release. However, what operation is triggering your exception? It seems odd that there is no diagnostic message. |
I've already worked around it by fetching the error codes from the LdapConnection. :) The issue is all from the same query: A simple I'm totally new to LDAP/AD. It's an enterprise scale world wide AD server net with 5 base DNs and 4 levels of OUs each to get down to the users: OU=USERS,OU="CITY",OU="COUNTRY",OU="FOO",DC=SUB,DC=EXAMPLEWAN,DC=COM No clue if this is bad by design. It was just a little suprise for me as the contract only told about AD connection for a single location. ;-) btw: Many thanks for your quick support! 🍻 |
Hi,
I'm currently working on an LDAP authentication against a damn huge (200k+ accounts) AD and have some issues with several queries. One thing is a user search which throws the
LdapConnectionException
in theQueryOperationHandler
. Sadly it doesn't contain any helpful message:It'd be great if the exception could expose the error code or do I miss something?
Cheers
Matthias
The text was updated successfully, but these errors were encountered: