Bug #5541: Filter of resource type Organization can result in error condition when trying to access organization resources - Foreman

Actions

Copy link

Bug #5541

closed

Filter of resource type Organization can result in error condition when trying to access organization resources

Added by Eric Helms over 10 years ago. Updated over 6 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Marek Hulán

Category:

Users, Roles and Permissions

Target version:

1.7.0

Difficulty:

Triaged:

Bugzilla link:

1098709

Pull request:

https://github.com/theforeman/foreman/pull/1726

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

1. Create new role
2. Create new user
3. Assign user to new role
4. Add filter to role of resource type 'Organization', select 'edit_organization' verb
5. Click organizations tab and select 'ACME_Corporation'
6. As the new user, with only the new role, do a PUT to /api/v2/organizations/1

Error Output:

{
"error": {
"message": "Field 'organization_id' not recognized for searching!",
"class": "ScopedSearch::QueryNotSupported"
}
}

Related issues 4 (1 open — 3 closed)

Actions

Copy link

Updated by Dominic Cleal over 10 years ago

Category set to Users, Roles and Permissions

Actions

Copy link

Updated by Dominic Cleal over 10 years ago

Related to Bug #5397: Architectures filter blows up if an organization is selected added

Actions

Copy link

Updated by Dominic Cleal over 10 years ago

Blocks Tracker #4552: New permissions/authorization system issues added

Actions

Copy link

Updated by Dominic Cleal over 10 years ago

Translation missing: en.field_release set to 16

Actions

Copy link

Updated by Dominic Cleal over 10 years ago

Target version set to 1.8.2

Actions

Copy link

Updated by Marek Hulán over 10 years ago

Status changed from New to Need more information

Could you please retest with develop branch? I think this was fixed in #5664 since you can't set taxonomy filters for resources that do not support it. See https://github.com/theforeman/foreman/commit/82b4749eeddabc542ebf1eaec6fdf2d76d2fdd75 for more details.

Actions

Copy link

Updated by Marek Hulán over 10 years ago

Related to deleted (Bug #5397: Architectures filter blows up if an organization is selected)

Actions

Copy link

Updated by Marek Hulán over 10 years ago

Is duplicate of Bug #5397: Architectures filter blows up if an organization is selected added

Actions

Copy link

Updated by Dominic Cleal over 10 years ago

Status changed from Need more information to Duplicate

Actions

Copy link

#10

Updated by Dominic Cleal over 10 years ago

Status changed from Duplicate to Feedback
Target version deleted (~~1.8.2~~)
Translation missing: en.field_release deleted (16)

Actions

Copy link

#11

Updated by Dominic Cleal over 10 years ago

Related to Bug #5664: Users permissions on hosts are not working properly with organizations added

Actions

Copy link

#12

Updated by Bryan Kearney over 10 years ago

Bugzilla link set to https://bugzilla.redhat.com/show_bug.cgi?id=1098709

Actions

Copy link

#13

Updated by Eric Helms over 10 years ago

Status changed from Feedback to New

While this has been fixed via taxonomy hiding for resource types that don't support it, the bug is still possible the API. For example,

POST /api/v2/filters

{
"role_id": 9,
"permission_ids": [98],
"organization_ids": [1]
}

Result: {
"id": 152,
"search": null,
"resource_type": "Organization",
"unlimited?": true,
"created_at": "2014-08-14T13:12:59Z",
"updated_at": "2014-08-14T13:12:59Z",
"role": {
"name": "Test Role",
"id": 9
},
"permissions": [ {
"name": "edit_organizations",
"id": 98,
"resource_type": "Organization"
}
],
"organizations": [ {
"id": 1,
"name": "Default_Organization"
}
],
}