mirror of
https://github.com/lldap/lldap.git
synced 2026-04-25 08:15:52 +03:00
[GH-ISSUE #196] Alternatives to using Admin for LDAP Check #75
Labels
No labels
backend
blocked
bug
cleanup
dependencies
docker
documentation
duplicate
enhancement
enhancement
frontend
github_actions
good first issue
help wanted
help wanted
integration
invalid
ldap
pull-request
question
rust
rust
tests
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/lldap-lldap#75
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @clbx on GitHub (Jun 23, 2022).
Original GitHub issue: https://github.com/lldap/lldap/issues/196
In all of the examples, and as far as I can tell, the Bind User always had to be admin. This is inherently insecure since the only user that applications can use has full access to the server. Adding a read_only group and/or adding the option for anonymous reads, would solve this issue.
@martadinata666 commented on GitHub (Jun 23, 2022):
Technically, afaik by default we already had
lldap_readonlygroup, we only need to create a user and add it to readonly group, or maybe another suggestion lldap can create one readonly user by default.And about the example, is about some familiarity and use lldap as easy as possible. Maybe we should create a doc about this security concerns like
yes you can use admin, but use readonly user with some tutorial create user with lldap_readonly@nitnelave commented on GitHub (Jun 23, 2022):
Indeed this can be achieved by creating a user, member of the lldap_readonly group. It hasn't been properly documented though, so if anyone of you wants to add something to the docs and link it from the readme, that would be welcome!
@clbx commented on GitHub (Jun 23, 2022):
lldap_readonly solves my issue, but an anonymous read option would also be super convenient.