Skip to content
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

Ability to admins control which type of group of users talk application can use on rooms. #1882

Closed
emersonkfuri opened this issue Jun 4, 2019 · 6 comments
Labels
1. to develop enhancement feature: api 🛠️ OCS API for conversations, chats and participants
Milestone

Comments

@emersonkfuri
Copy link

I have several LDAP security groups with a huge number of users which I use to control access to external storages in my NC instance.

I had to disable autocomplete to prevent users from clicking in those groups on mobile and open huge rooms causing spam into NC. With this last update on Android talk (don't know about IOS), users can now search for users and group. This feature is great but in my case, it opened the same problem as before.

It would be really great if administrators could filter which type of group of users talk application can address, like LDAP groups, personal groups, circles or else.

Thank you,

EHKP

@moarf56
Copy link

moarf56 commented Jun 9, 2019

I have a litle instance of NC with groups, and I search the same thing !
The ability to choose who can speak with someone.

If someone want help for testing, I'm here !

ThX

@nickvergessen
Copy link
Member

@emersonkfuri I guess best would be to not deploy the groups with the LDAP backend.
The thing is, we use the same endpoint as the file sharing dialog. So you can only fix it for both in one go, or not at all.

But also when I turn off autocomplete, people have to search the full group name Nextclou as search term will not bring up the Nextcloud group.
If your group name is too easily guessable that is a different issue of course. You could add an emoji or something 🙈

@emersonkfuri
Copy link
Author

Hello @nickvergessen! It would be too much complex to do it at this endpoint? Besides to "fix" it on one go, other apps in the future may benefit from it.

Regard the group's names, they are pretty intuitive because they're created and used by an AD Domain.

@moarf56
Copy link

moarf56 commented Jul 1, 2019

@emersonkfuri I guess best would be to not deploy the groups with the LDAP backend.
The thing is, we use the same endpoint as the file sharing dialog. So you can only fix it for both in one go, or not at all.

But also when I turn off autocomplete, people have to search the full group name Nextclou as search term will not bring up the Nextcloud group.
If your group name is too easily guessable that is a different issue of course. You could add an emoji or something 🙈

But for an user like me ? I use nextcloud with local NC user. I can turn off autocomplete only for the talk app ?

Thx

@nickvergessen nickvergessen added this to the 💔 Backlog milestone Jul 2, 2019
@nickvergessen nickvergessen added feature: api 🛠️ OCS API for conversations, chats and participants and removed needs info labels Jul 2, 2019
@nickvergessen
Copy link
Member

This is just too specific, so it is unlikely to get implemented at the moment, because there are other things way higher on the priority list.

@nickvergessen
Copy link
Member

As per #1464 and nextcloud/server#25658 apps are supposed to respect the share settings, so if something like a group filter is wished, it needs to be implemented on the server and then applies to all apps at the same time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. to develop enhancement feature: api 🛠️ OCS API for conversations, chats and participants
Projects
None yet
Development

No branches or pull requests

3 participants