Show user display name on external share confirmation dialog
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.
When receiving a remote share from another server, the username show to the user is the Nextcloud login/ID.
This happens even with a trusted server or a known user (from contacts/lookup server).
This can be complicated to read when using user backend like LDAP, the login/ID is a UUID by default.
An example :
Describe the solution you'd like
When a remote share is received, Nextcloud should use a known display name (contacts, trusted servers, lookup server, etc…).
This aims to mimic the behavior of the share tab on the file informations with a remote share, this show the known display name.
The same share after being accepted in the said share tab :
Describe alternatives you've considered
Change the Nextcloud login name in the LDAP backend expert parameters.
This can create collision between user and need to recreate all accounts from scratch.
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
Start by locating the external share confirmation dialog and the existing display-name handling used in the file information share tab. Trace how remote-share identities are resolved from contacts, trusted servers, or the lookup server. Done means the confirmation dialog shows the known display name when available while retaining a usable fallback.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100