Bug #6150

Users need locations added even if "All users" is ticked

Added by Scott Wade almost 4 years ago. Updated 7 months ago.

Status:Ready For Testing
Priority:Normal
Assigned To:Kavita Gaikwad
Category:Organizations and Locations
Target version:Team Anurag Iteration 21
Difficulty: Bugzilla link:1321543
Found in release:1.5.0 Pull request:https://github.com/theforeman/foreman/pull/4111
Story points-
Velocity based estimate-

Description

I am using locations, but not organizations. I have several locations defined. I have "All users" ticked on the Users sub-tab within each location.

I am using authentication with LDAP backends. For my LDAP sources, I have "Automatically create accounts in Foreman" ticked. My accounts are filtered with an LDAP filter, and automatic account creation works fine. My Anonymous role (which applies to these users) has the "view_locations" permission granted.

However, when a user logs in, they are not able to view any locations under the Administer -> Locations menu. And the "Any Context" menu in the top left does not list any locations in its dropdown.

Using an admin user (or a user who can edit other users), I can add locations manually to a specific user. If this user re-logs in, then they are able to view locations as expected.

It seems like the "All users" being specified on the Users sub-tab of the Location is not taking effect. Or I'm not understanding its intended purpose.

Dominic and I discussed this on IRC some. I can provide any information that might help. This is a new Foreman setup that we're just getting underway.


Related issues

Related to Foreman - Feature #6094: Ability to add usergroups to organizations New 06/06/2014
Related to Foreman - Tracker #10022: Taxonomies related issues New 04/05/2015
Related to Foreman - Feature #16624: Make auth sources taxable Closed 09/20/2016
Duplicated by Foreman - Bug #14499: Assigning organization and location by enabling "All User... Duplicate 04/06/2016

History

#1 Updated by Dominic Cleal almost 4 years ago

  • Category set to Organizations and Locations

#2 Updated by Dominic Cleal over 3 years ago

  • Related to Feature #6094: Ability to add usergroups to organizations added

#3 Updated by Dominic Cleal about 2 years ago

  • Duplicated by Bug #14499: Assigning organization and location by enabling "All Users" checkbox doesn't work as expected added

#4 Updated by Marek Hulán about 2 years ago

#5 Updated by Ohad Levy about 2 years ago

  • Bugzilla link set to 1321543

#6 Updated by Kavita Gaikwad over 1 year ago

  • Assigned To set to Kavita Gaikwad
  • Target version set to Team Anurag backlog

#7 Updated by Kavita Gaikwad over 1 year ago

After debugging the issue, found few things as below.

1. Not only users tab but all sub-tabs under location/organization are having similar behaviour.

2. Whenever user selects check-box "All users", non-selected users remains in select panel not moved to selected panel. After saving the taxonomy, those changes are not taking effect.

3. Lets say "All users" option checked under location and we try to create new user. Location is neither showing on the UI i.e user creation form nor assigned to user after save.
But if you see under edit location page, new user is listed under "selected" panel on users sub tab.

Please could anyone provide more details on above points. Exactly, What should be the behaviour of "All select" check-box on each sub-tab under taxonomy.

#8 Updated by The Foreman Bot over 1 year ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/4111 added

#9 Updated by Kavita Gaikwad over 1 year ago

  • Target version changed from Team Anurag backlog to Team Anurag Iteration 7

#10 Updated by Marek Hulán 10 months ago

The original issue reported here was already fixed by #16624 in Foreman 1.14. By assigning taxonomy to to LDAP auth source, all users auto-created from this auth source will be configured to be assigned into auth source's locations. The PR fixes the usability issue so that using ignore checkbox would be less confusing as it would in reality add real associations between the resources and a given taxonomy.

#11 Updated by Marek Hulán 10 months ago

#12 Updated by Kavita Gaikwad 9 months ago

  • Target version changed from Team Anurag Iteration 7 to Team Anurag Iteration 19

#13 Updated by Kavita Gaikwad 9 months ago

  • Target version changed from Team Anurag Iteration 19 to Team Anurag Iteration 20

#14 Updated by Kavita Gaikwad 8 months ago

  • Target version changed from Team Anurag Iteration 20 to Team Anurag Iteration 21

Also available in: Atom PDF