You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an user, I can find all usernames in my instance by using the "Invitations" feature.
To Reproduce
As an admin, "Allow username autocompletion in share dialog. If this is disabled the full username or email address needs to be entered" is disabled
Create a poll as user
Go to Details, then Shares
Start typing something in the box under " Invited users will get informed immediately via eMail!"
Expected behavior
As an user, I should not be able to see all usernames existing on the instance.
I should be able to add an user for an invitation only if I know his/her username fully, not my guessing it by writing some letters only.
Information about your polls installation
1.30
Fresh installation
Appstore
Information about your Instance of Nextcloud/ownCloud
Hello,
Aren't invitations supposed to be limited to groups?
When user of a group tries to share a poll, the list of other groups is proposed. Is there any trick to restrict to the group of the user?
Regards.
Activity
dartcafe commentedon Apr 4, 2020
Interesting, I thought, this is handled by the core, when suing the user API. We will have to check this.
oafgip commentedon Jun 9, 2020
Hello,
Aren't invitations supposed to be limited to groups?
When user of a group tries to share a poll, the list of other groups is proposed. Is there any trick to restrict to the group of the user?
Regards.
dartcafe commentedon Jun 12, 2020
No. There is no limitation.
fix #881 - respect autocompletion restrictions from share settings
dartcafe commentedon Dec 21, 2020
#1307 uses another search which respects the autocomplete limitations of the share settings (users and groups).
Merge pull request #1307 from nextcloud/search-users
github-actions commentedon Jun 6, 2024
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.