[Bug]: Restrict users to only share with users in their groups does not work

[pabloeisenhut]

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

The function Restrict users to share only with users in their groups no longer works. Regardless of whether the function is activated or not, users cannot see each other outside their groups.

Steps to reproduce

1. create two users who are each in their own group
2. check whether the function Restrict users to share only with users in their groups is deactivated
3. log in to one of the users and open the share dialog of a file

Expected behavior

the user you are logged into should be able to see the other user in the share dialog and share files.

Installation method

Community Docker image

Nextcloud Server version

28

Operating system

None

PHP engine version

None

Web server

None

Database engine version

PostgreSQL

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

[szaimen]

cc @Fenn-CS @sorbaugh

[pabloeisenhut]

In my case it also affects Talk. Users cannot see each other. As described in nextcloud/spreed#8990

[pabloeisenhut]

Is there anything I can do to help?

[Fenn-CS]

Hello @pabloeisenhut I was not able to reproduce this bug on 28, are you still able to see this error! If so yes then you can jump on a call with me and help me reproduce it or simply provide more information here.

[pabloeisenhut]

Hey @Fenn-CS , the error still exists, I think we can solve it faster with a call.

[Fenn-CS]

@pabloeisenhut if you are available now you can join me here : https://cloud.nextcloud.com/call/5051630186

Otherwise, please kindly leave me a message in there so we can arrange an appointment.

[pabloeisenhut]

@Fenn-CS I can be reached today from 4 p.m., is that okay with you?

[Fenn-CS]

@Fenn-CS I can be reached today from 4 p.m., is that okay with you?

Please can you use the talk link? It would only be up for a limited amount of time.

I mean we can actually text on the link to avoid spamming this ticket.

[pabloeisenhut]

@Fenn-CS The link requires an account or has expired? Feel free to create an account if that's possible, I wanted to join the public Design Team group anyway.

[Fenn-CS]

@Fenn-CS The link requires an account or has expired? Feel free to create an account if that's possible, I wanted to join the public Design Team group anyway.

It's open now for you to join as a guest.

[pabloeisenhut]

Okay, by try and error I have found the mistake. It's because of this setting:

In my opinion, the setting gives the impression that by activating these options, functions are added and not restricted.

The documentation explains these settings well, but I find the options misleading from the wording in the settings.

I think the wording should definitely be changed. For example to:

• Only allow username autocompletion to users within the same groups and limit system address books to users in the same groups

• Only allow username autocompletion to users based on phone number integration

[Fenn-CS]

Fair point now proposed correct wording : #46830