https://github.com/lldap/lldap logo
marcel - Anyone tried with https://www.npmjs.co...
# troubleshooting
m
Anyone tried with https://www.npmjs.com/package/activedirectory ldapjs? I think Im missing some attributes as the node library is failing to distinguish between group DNs and "other" DNs returned from LLDAP.
a
message has been deleted
n
Do you have an example of query that it's submitting, some results, and what it expects/error logs?
m
After looking over the node module code I think the response from the lldap is missing some attributes according which the node modules distinguishes the types of objects - i think Im missing the distinguishedName and objectClass definitions in the lldap reply for that particular query. im unsure 100% yet which ones.
Possibly memberOf . Im unsure whether the user attributes work at the moment with the latest lldap docker image - looks like they dont.
Yup, found this in lldap logs
Copy code
2024-07-22T14:22:59.951698814+00:00  DEBUG    │  ┝━ do_search [ 819µs | 0.25% / 0.64% ]
2024-07-22T14:22:59.952303136+00:00  DEBUG    │  │  ┝━ 🐛 [debug]:  | request.base: "dc=xxx, dc=bbb" | scope: Global
2024-07-22T14:22:59.952305863+00:00  DEBUG    │  │  ┝━ get_user_list [ 189µs | 0.01% / 0.15% ]
2024-07-22T14:22:59.952310923+00:00  WARN     │  │  │  ┝━ 🚧 [warn]: Ignoring unknown user attribute "member" in filter.\n\
and few more down the line
Copy code
2024-07-22T14:22:59.953409421+00:00  DEBUG    │  │  ┝━ expand_attribute_wildcards [ 7.27µs | 0.01% ] ldap_attributes: ["dn", "cn", "description", "groupType", "objectCategory", "objectClass", "member"]
2024-07-22T14:22:59.953416664+00:00  DEBUG    │  │  │  ┕━ 🐛 [debug]:  | resolved_attributes: ["dn", "cn", "description", "groupType", "objectCategory", "objectClass", "member"]
2024-07-22T14:22:59.953422531+00:00  WARN     │  │  ┝━ 🚧 [warn]: Ignoring unrecognized group attribute: description\n\
                               To disable this warning, add it to "ignored_group_attributes" in the config.
2024-07-22T14:22:59.953423805+00:00  WARN     │  │  ┝━ 🚧 [warn]: Ignoring unrecognized group attribute: grouptype\n\
                               To disable this warning, add it to "ignored_group_attributes" in the config.
2024-07-22T14:22:59.953424787+00:00  WARN     │  │  ┝━ 🚧 [warn]: Ignoring unrecognized group attribute: objectcategory\n\
                               To disable this warning, add it to "ignored_group_attributes" in the config.
2024-07-22T14:22:59.953430839+00:00  WARN     │  │  ┝━ 🚧 [warn]: Ignoring unrecognized group attribute: description\n\
                               To disable this warning, add it to "ignored_group_attributes" in the config.
2024-07-22T14:22:59.953431619+00:00  WARN     │  │  ┝━ 🚧 [warn]: Ignoring unrecognized group attribute: grouptype\n\
                               To disable this warning, add it to "ignored_group_attributes" in the config.
2024-07-22T14:22:59.953447946+00:00  WARN     │  │  ┕━ 🚧 [warn]: Ignoring unrecognized group attribute: objectcategory\n\
                               To disable this warning, add it to "ignored_group_attributes" in the config.
....and the docker build is failing with
Copy code
error: failed to compile `wasm-pack v0.13.0`, intermediate artifacts can be foun                                                                                                                                   d at `/tmp/cargo-installsE8E2Y`

Caused by:
  package `clap v4.5.9` cannot be built because it requires rustc 1.74 or newer,                                                                                                                                    while the currently active rustc version is 1.69.0
  Try re-running cargo install with `--locked`
error: failed to compile `cargo-chef v0.1.67`, intermediate artifacts can be fou                                                                                                                                   nd at `/tmp/cargo-installCXBjUB`

Caused by:
  package `clap_lex v0.7.1` cannot be built because it requires rustc 1.74 or ne                                                                                                                                   wer, while the currently active rustc version is 1.69.0
  Try re-running cargo install with `--locked`
     Summary Failed to install wasm-pack, cargo-chef (see error(s) above).
error: some crates failed to install
n
Alright, there's a bunch of separate things here: - distinguished name is always returned (usually as dn), it's necessary for an LDAP response. Object class is, I think, also always returned? Though it might only be if it's in the requested attributes. The verbose LLDAP logs would show us the query, that would be helpful. - the unrecognized member attribute in the filter means that we requested some users with a group-only filter (member is for groups, memberOf for users). That might just be because the request is generic and requesting everything. Again, verbose logs would help. - the other unrecognized group attributes are just this, the groups don't have this field. If they're important, you can create them. - finally, the docker build: the root docker file is not as well maintained, but you'd just need to update the base image to something with a more recent rust version. The one used for producing the official image is in .github/
Coming back to this, can you post the verbose LLDAP logs? That would get us most of the way to a good diagnosis