-
-
Notifications
You must be signed in to change notification settings - Fork 169
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
[FEATURE REQUEST] Return schema in RootDSE for better compatibility with Apache Directory Studio Browser #893
Comments
I don't know that much about rootDSE and how to respond with the schema. In the spirit of my limited time and to avoid reading the RFC, could you provide an example of a rootDSE response you'd like to see? |
I am not too sure myself. I actually only extremely recently made myself familiar with LDAP because I wanted to use your tool in my homelab, and I had needs for work. Some searching came up with what I think might be a good explanation of rootDSE here: link What I think this means is that there is no schema returned when it (Apache Directory Studio) tries to fetch the root of the directory server. What this results in is the following error message. Also, if there is no "namespaceless" root, then Apache Directory Studio is restricted to a connection to LLDAP that has a baseDN of I hope this clarifies. I could also be way off base as I am very very new to this stuff and may not have any idea what I am talking about, but I am trying to learn. By the way... I really like your LLDAP tool. It is amazing for small homelabs to dip feet into LDAP. My friends and I that are on the homelab journey together are enjoying its use. I appreciate the hard work. |
@Firstyear hey, do you know what's needed in the rootDSE for this? I made the minimum effort to be compliant, but this is stretching my knowledge. I guess I need to declare and implement the DC level above the OUs, and declare a schema? |
I'll save you the trouble of reading the (whole) RFC: https://www.rfc-editor.org/rfc/rfc4512#section-4.4 """ So this really glosses over whats going on. In the rootdse you have:
subschemaSubentry is operational, so only return it on The client then searches with that as the base dn, you just respond with a single entry with a ton of attributes representing the schema. These entries are defined in https://www.rfc-editor.org/rfc/rfc4512#section-4.2 again with the usual level of "specific but not clear" as we would expect from an LDAP rfc. And easy way to "cheat" and check this would be to look at what something else does. So here's an ldif I prepared for you.
|
Oh, geez, it's more complicated than I thought... I was hoping for adding a couple of lines to the hardcoded rootDSE 😅 Thanks a lot! |
but for once it's not twice as complicated as it should be. |
Motivation
I want to be able to use Apache Directory Studio Browser to browse LLDAP server
Describe the solution you'd like
When creating the connection to LLDAP in Apache Directory Studio, you must enter the baseDN manually because LLDAP is "Missing schema location in RootDSE" and the baseDN(s) cannot be fetched.
I can make this work half way by creating two connections and manually identifying one baseDN as
ou=people,dc=example,dc=com
orou=groups,dc=example,dc=com
. However, they must be separate connections. It would be nice if there was an OU one level up or some other way to identify the baseDN. Even better would be for that baseDN to be fetchable by the Apache Directory Studio.The text was updated successfully, but these errors were encountered: