Bug #5489
closed
Permission migration script can create invalid search conditions
Added by Marek Hulán almost 10 years ago.
Updated almost 6 years ago.
Category:
Users, Roles and Permissions
|
|
Description
after migration a user reported filters with search phrases like "(() or (compute_resource_id = 2))" which raises scoped search exceptions, we should go over the whole migration script and make sure we can't detect empty conditions
Related issues
1 (1 open — 0 closed)
- Blocks Tracker #4552: New permissions/authorization system issues added
one clue (but worth of checking all condition generating)
the only users who had the incorrect search string syntax were ones that had ownership of more than one hostgroup
- Target version set to 1.8.3
- translation missing: en.field_release set to 4
- Status changed from New to Assigned
- Assignee set to Dominic Cleal
To reproduce:
0. Use pre-#812 Foreman
1. Create a user with the "View hosts" role (#5540)
2. Edit the user, add two types of filter: a domain filter + a host group filter. Do not tick owned hosts.
3. Migrate to post-#812
4. Check the custom role + filter added, you'll see: (() or (domain_id = 1)) or (hostgroup_id = 1)
- Status changed from Assigned to Ready For Testing
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Also available in: Atom
PDF
Updated by 
Updated by