Zepmann

> Feel free to try it out, it should greatly simplify handling of attributes (but it's not user friendly, only admin friendly) I prefer the term [user-centric](https://wiki.archlinux.org/title/Arch_Linux#User_centrality). :wink: If there...

@jakob42 Custom attributes only work in the current development version. There hasn't yet been a stable release of LLDAP that includes it.

@nitnelave You can always make a stable release in which you label some features experimental, such as custom attributes. This will temper expectations, especially since this new feature is only...

Note that VERSION of release 13.0.1 contains: ``` 13.0.0 ``` For anyone thinking they need to rely on /VERSION inside a container when using bash (e.g. when using user-patches.sh): you...

@TheRealGramdalf > In order to keep lldap simple, adding unix sockets as an option may be out of scope. Just because lldap would support unix sockets would not have to...

@nitnelave That's a good proposal. I agree that unix sockets are an advanced topic, so they should not be mentioned in integration examples in the documentation. Maybe over time you...

Fun fact: The compatibility with LDAP features that lldap supports is so good that OpenLDAP's `ldappasswd` tool can also be used to set a user's password. It was originally one...

> It seems like the frontend-agnostic API is paying off. Well, kinda. Using GraphQL is an... interesting but confusing experience. Therefore this feature request still stands. It would be nice...

> In bash, I can definitely picture that :D Most languages have a framework that can generate some code based on the schema, so it's much simpler to use. What...

Recently had some time to work on this. Updated the task list. I want to add at least basic attribute setting/clearing for both users and groups, and listing all user-defined...