[GH-ISSUE #285] Add support for PosixAccount #103

Closed
opened 2026-02-27 08:15:15 +03:00 by kerem · 1 comment
Owner

Originally created by @Zerwin on GitHub (Aug 12, 2022).
Original GitHub issue: https://github.com/lldap/lldap/issues/285

Would it be possible to add the necessary fields to support the PosixAccount Type ?
Currently already implemented fields that would be required for this are cn and uid while uidNumber, gidNumber and homeDirectory are missing.
There is also the optional fields loginShell, gecos, description, authPassword but I think these are for now not so important.

The reason I ask for support of this is that this would enable using LLDAP for logging into Linux Machines via nslcd. This is one of my prime use-cases for LDAP and something I would hope to see implemented in this project.
(Side Note: I love the project, setting things up was about 20x times less work than with OpenLDAP, even for LDAPS. Thanks for the great work)

I hope this isn't deemed out of scope for this project, I would love to have basically all my use cases covered by LLDAP.

Originally created by @Zerwin on GitHub (Aug 12, 2022). Original GitHub issue: https://github.com/lldap/lldap/issues/285 Would it be possible to add the necessary fields to support the [PosixAccount](https://ldapwiki.com/wiki/PosixAccount) Type ? Currently already implemented fields that would be required for this are [cn](https://ldapwiki.com/wiki/Cn) and [uid](https://ldapwiki.com/wiki/Uid) while [uidNumber](https://ldapwiki.com/wiki/UidNumber), [gidNumber](https://ldapwiki.com/wiki/GidNumber) and [homeDirectory](https://ldapwiki.com/wiki/HomeDirectory) are missing. There is also the optional fields [loginShell](https://ldapwiki.com/wiki/LoginShell), [gecos](https://ldapwiki.com/wiki/Gecos), [description](https://ldapwiki.com/wiki/Description), [authPassword](https://ldapwiki.com/wiki/AuthPassword) but I think these are for now not so important. The reason I ask for support of this is that this would enable using LLDAP for logging into Linux Machines via nslcd. This is one of my prime use-cases for LDAP and something I would hope to see implemented in this project. (Side Note: I love the project, setting things up was about 20x times less work than with OpenLDAP, even for LDAPS. Thanks for the great work) I hope this isn't deemed out of scope for this project, I would love to have basically all my use cases covered by LLDAP.
kerem 2026-02-27 08:15:15 +03:00
  • closed this issue
  • added the
    duplicate
    label
Author
Owner

@nitnelave commented on GitHub (Aug 12, 2022):

Hi! I think I'll solve this as part of https://github.com/nitnelave/lldap/issues/67 : you'll be able to have all the fields you want :)

<!-- gh-comment-id:1213552172 --> @nitnelave commented on GitHub (Aug 12, 2022): Hi! I think I'll solve this as part of https://github.com/nitnelave/lldap/issues/67 : you'll be able to have all the fields you want :)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/lldap-lldap#103
No description provided.