Use LDAP user name instead of UUID for federated cloud id
Nobody has claimed this yet.
- #31015 by @itmanagerro — closed without merging
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
Nextcloud (up to version 12.0.0) generates federated cloud ids of the shape uid@server. This leads to inconvenient cloud ids in case of LDAP users because the LDAP user app configures the UUID as Nextcloud uid per default. This is changeable via the LDAP configuration panel but changes only behaviour for new users (because I cannot clear the LDAP user mapping in a production environment).
It would be nice if this would be configurable on the federation cloud id level to generate cloud ids for LDAP users from the LDAP username.
Maybe the new cloud id api from pull request #3297 can be handy to implement this feature?
(s. also Nextcloud Forum here: https://help.nextcloud.com/t/changing-the-internal-user-name/8924)
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
Read the cloud ID API referenced in pull request #3297 and the LDAP configuration behavior described in this issue. Trace how federated IDs are generated for existing LDAP users, then establish how username-based IDs could be configured without requiring production user remapping and how the result should be verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100