Hi 🙂 not sure if this is per design... I want to query for a user-attribute that is of type List. When doing ldapsearch and only one attribute (e.g. mailalias) for an object is set, the return is as expected. However, when I set a second mailalias, nothing is returned anymore... Any ideas how to tackle this? ldapsearch -x -H ldap://lldap -D "uid=admin,ou=people,dc=example,dc=com" -w secret -b "dc=example,dc=com" "(&(objectClass=inetOrgPerson)(mailAlias=alias@example.com))" mail

That's a somewhat well known design flaw in LLDAP (for now!)

thanks, sounds good. will implement the workaround. is that also suggested somewhere in the documentation?

It should be! If it's missing we should add it

is there a estimate when the design-flaw could be fixed?

None whatsoever 🙂

understandable.. well-known+design-flaw sounds like it’s very difficult to tackle…

It's also that I don't have free time anymore, so it's hard to implement. I've got the design more or less figured out

Ah, I ran into this now as well. Fixed list of alias1 alias2 and so on won't cut it, because sometimes I want 50 aliases for a user. Is there already a discussion I could attach myself to? And if I would use this to learn rust (and I just might not), would you be interested in a pull request or is that something you would prefer to do yourself? (whenever you find the time of course!)

Brand New issue to track that: https://github.com/lldap/lldap/issues/1133

Yeah, I looked at the code but I hoped rust would come easier to me since I did some stuff in golang. But I'm not a dev by trade so some things come harder to me.