Set user profile information from LDAP/AD attributes
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Is your feature request related to a problem? Please describe.
The new user profiles that were enabled with v23 rely on the user to be filled out.
Especially the "Organisation" and "Function" attributes would benefit if they were managed centrally to prevent e.g. typos.
Describe the solution you'd like
It would be more helpful if they were pre-filled with attributes from our LDAP/AD.
"Function" could be set by the AD attribute "physicalDeliveryOfficeName".
In the LDAP admin settings in the Advanced-Tab it is already possible to link AD attributes to specific Nextcloud user attributes.
It would just need another row/attribute to add there.
Like this:

Describe alternatives you've considered
"Organisation" could be set by the admin in the settings where the whole user profile feature gets enabled.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are named. Start by locating the LDAP admin settings Advanced tab and the existing mapping of LDAP/AD attributes to Nextcloud user attributes; the work is done when Function and Organisation can be populated from centrally mapped attributes, including physicalDeliveryOfficeName for Function.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100