mirror of
https://github.com/lldap/lldap.git
synced 2026-04-25 08:15:52 +03:00
[GH-ISSUE #171] Add support for the JpegPhoto attribute #65
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#65
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 @soupglasses on GitHub (May 22, 2022).
Original GitHub issue: https://github.com/lldap/lldap/issues/171
This is a issue asking for the inclusion of the JpegPhoto attribute from the InetOrgPerson class.
This adds a nice quality of life experience to help manage and centralize the profile pictures for the users under lldap.
One example of a service using
JpegPhotowould be Nextcloud and itsuser_ldap_authmodule: https://docs.nextcloud.com/server/latest/admin_manual/configuration_user/user_auth_ldap.html#nextcloud-avatar-integration@nitnelave commented on GitHub (Jun 6, 2022):
This shouldn't be too hard since I planned ahead and allocated an "Avatar" column in the users table. It needs a bit of massaging to get it exposed to the LDAP interface though.
@nitnelave commented on GitHub (Aug 8, 2022):
I have a PR that mostly solves the issue: users can add their own avatar, and it's served as
jpegPhotoin LDAP.However, note that adding support to the migration tool is blocked by https://github.com/inejge/ldap3/issues/86.
@nitnelave commented on GitHub (Aug 8, 2022):
@imsofi Do you think you could test the PR #284 ?
@soupglasses commented on GitHub (Aug 9, 2022):
Sadly i do not use lldap for my services anymore as i migrated to openldap completely. I may still see if i can test it in a container environment. But i will not be able to test how it integrates into things like nextcloud I am afraid.
@nitnelave commented on GitHub (Aug 9, 2022):
If your openldap setup is similar to lldap (single ou=people with all users, single ou=groups with all groups) then it should be fairly simple to import the data into lldap, with the migration tool (apart from the passwords). But I understand if you don't want to get into that.
EDIT: I merged the PR to make it easier to test: you should be able to just fetch
:latestand get a working container.@soupglasses commented on GitHub (Aug 9, 2022):
Yeah, sadly my switch to openldap was to gain more flexibility with user creation and acl. So it is no longer easy to migrate back into lldap or another similar solution.
@nitnelave commented on GitHub (Oct 14, 2022):
Marking as done, we'll see if any issue crops up.