Project

General

Profile

Actions
Copy link

Bug #12118

closed

AssociationAuthorizer should ask model for alternative permission names

Added by Stephen Benjamin almost 9 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Stephen Benjamin
Category:
Users, Roles and Permissions
Target version:
1.10.0
Difficulty:
Triaged:
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman/pull/2803
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Current assumes some magic: a House model would always be "view_houses", but maybe you want a different permission name. Especially for plugins the code generates stuff like "view_foreman_salt/houses"

Related issues 1 (0 open — 1 closed)

Has duplicate Foreman - Bug #11408: Plugin permissions are broken when using multiple selectsDuplicate08/18/2015Actions
Actions
Copy link
 #1

Updated by The Foreman Bot almost 9 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/2803 added
  • Pull request deleted ()
Actions
Copy link
 #2

Updated by Dominic Cleal almost 9 years ago

  • Translation missing: en.field_release set to 63
Actions
Copy link
 #3

Updated by Anonymous almost 9 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions
Copy link
 #4

Updated by Stephen Benjamin almost 9 years ago

  • Has duplicate Bug #11408: Plugin permissions are broken when using multiple selects added
Actions
Copy link

Also available in: Atom PDF