https://github.com/lldap/lldap logo
lnnwvr - i have a very strange behavior in comb...
# troubleshooting
a
message has been deleted
j
So you cannot login? Can you show the output of
occ ldap:show-config
(docker often
docker exec -it -u 33 nextcloud-container ./occ ldap:show-config
)
l
no i can .. i want to search for users (calender invite) with first or lastname .. i just find the code in lldap:
Copy code
UserFieldType::Attribute(_, _, _)
                | UserFieldType::ObjectClass
                | UserFieldType::MemberOf
                | UserFieldType::Dn
                | UserFieldType::EntryDn
                | UserFieldType::PrimaryField(UserColumn::CreationDate)
                | UserFieldType::PrimaryField(UserColumn::Uuid) => Err(LdapError {
                    code: LdapResultCode::UnwillingToPerform,
                    message: format!(
                        "Unsupported user attribute for substring filter: {:?}",
                        field
                    ),
                })
this just creates errors for sn=blabla* .. becuase sn is an attribute. Idk why its implemented that way.
j
Oh, thats out of my depth then.
n
That's a limitation of the design, we can't (currently) do substring searches for anything other than uid and email
There's an open issue to improve that, but it's a pretty big effort
l
yeah i just debugged into the sqlite and saw how attributes are stored 😦
then i check if i can convince nextclouse to search for cn=* foo * instead of cn=foo* only
n
The rationale at the time was "it makes the DB simpler, and anyway, who*really* needs to do substring searches or search in a list of elements, apart from uid/mail?"
j
Didn't think lldap would be that successful? 😉
n
*foo*
is not going to work either
l
yeah .. hardcoding firstname and lastname and dont make it an "primary value" is now comming back to its developers
n
That's part of the reason, but at that point LLDAP was already pretty successful
l
Copy code
*foo*
on cn should work
n
It's more than just first last name. Mail aliases for instance
Ah right
l
unfortunately its also not easy/possible to change ho nextcloud composes the search