-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Guest users can have the same name #142
Comments
This is a general problem. Every user can change the display name ('full name') to an existing one. You can't even say in the sharing dialog which one is the one you need. In my example (see screenshot) I created two users, "test2" and "test3" and changed their display names to "hallo". We therefore need a general solution for this. Options:
This is nothing guests-specific and needs a core ticket. Probably there already is one. @PVince81 when time permits. |
Raised here: owncloud/core#28979 |
The administrator is able to block users to modify the But there is still this bug: owncloud/core#27442 |
with the latest master you cannot specify a name any more, you create guests directly by email address. So this bug is obsolete on the guests side |
Hmm right, the display name. Reopening. |
Hmm right, the display name. Reopening. |
This is solved with the "solution for indistinguishable display names" we introduced with 10.0.4, right? |
Guests are able to set display names, so two guests could set the same name. But if the admin set the new core option to always display the email address in the sharing autocomplete, then it will be possible to distinguish these users, yes. |
Assuming that the API response also contains the mail address if enabled I close this now. Please reopen if this is not the case. A general guest identifier like an icon or "(guest)" would still be very helpful but that's actually another topic. |
@pmaier1 Guest users with different email can have the same name in oC. Should we add a restriction in other to avoid it?
The text was updated successfully, but these errors were encountered: