Feature #5389: usergroup autocompletion when adding a permission does not work when not direct member of allowed group - RhodeCode CE/EE - RhodeCode - issues

Custom queries

Backlog
Bugburner
Current Work
Current Work - Done
Current Work - Stuck
Epics
Last Iteration 35
QA Backlog
Refinement
To inspect

Actions

Copy link

Feature #5389

closed

usergroup autocompletion when adding a permission does not work when not direct member of allowed group

Added by Gildas Fargeas over 6 years ago. Updated almost 6 years ago.

Status:

Closed

Priority:

Low

Assignee:

Category:

Target version:

v4.10

Start date:

20.09.2017

Due date:

% Done:

Estimated time:

Sorting:

Commit Number:

Description

Usergroup A has read permissions set to another usergroup B containing both usergroups and users.
When trying to add a permissions to usergroup A in any repo, it won't autocomplete if current user is in a nested group and not a direct member of usergroup B.

History
Notes
Property changes

Actions

Copy link

Updated by Marcin Kuzminski [CTO] over 6 years ago

Target version set to v4.10

Actions

Copy link

Updated by Marcin Kuzminski [CTO] over 6 years ago

Status changed from New to In Progress

Actions

Copy link

Updated by Marcin Kuzminski [CTO] over 6 years ago

Hi,

We're not sure if this ticket is 100% clear to us. What do you mean by:

usergroup B containing both usergroups and users.
Does it mean permissions?
When trying to add a permissions to usergroup A in any repo.
You mean add usergroup A as permissions to a repo right ?

Finally:
-it won't autocomplete if the current user is in a nested group and not a direct member of usergroup B.

IT means that entering usergroup A won't autocomplete. But still not clear in what exact situation, is it an member of some other group in usergroup B.

Would be great to provide some more examples if possible.

Thanks

Actions

Copy link

Updated by Gildas Fargeas over 6 years ago

Ok, I had to start from scratch to be more clear and that opened my eyes on a discrepancy in my default permissions settings.
I had the inheritance from the default user unmarked so when trying to allow all groups to be readable from any user, this was not working.

The whole situation was in fact an inheritance problem on our server and even when I tested with a simple user, it looked like some groups were not visible to only a subset of user !

Sorry about that, this issue was particularly tricky to identify on my side.
I have, however :), a suggestion regarding the autocompletion or permissions suggestions! It is not sorted alphabetically. Pretty minor stuff I know...

Marcin Kuzminski [staff] wrote:

Hi,

We're not sure if this ticket is 100% clear to us. What do you mean by:

usergroup B containing both usergroups and users.
Does it mean permissions?

When trying to add a permissions to usergroup A in any repo.
You mean add usergroup A as permissions to a repo right ?

Finally:
-it won't autocomplete if the current user is in a nested group and not a direct member of usergroup B.

IT means that entering usergroup A won't autocomplete. But still not clear in what exact situation, is it an member of some other group in usergroup B.

Would be great to provide some more examples if possible.

Thanks