Project

General

Profile

Bug #12118

AssociationAuthorizer should ask model for alternative permission names

Added by Stephen Benjamin almost 4 years ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Category:
Authorization
Target version:
Difficulty:
Triaged:
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:

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

Has duplicate Foreman - Bug #11408: Plugin permissions are broken when using multiple selectsDuplicate2015-08-18

Associated revisions

Revision b6b977aa (diff)
Added by Stephen Benjamin almost 4 years ago

fixes #12118 - query model for alternative permission names

Revision aee187b2 (diff)
Added by Stephen Benjamin almost 4 years ago

fixes #12118 - query model for alternative permission names

(cherry picked from commit b6b977aaa0ca4ee4ff7cc59de234f1cbba54c5f4)

History

#1 Updated by The Foreman Bot almost 4 years ago

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

#2 Updated by Dominic Cleal almost 4 years ago

  • Legacy Backlogs Release (now unused) set to 63

#3 Updated by Anonymous almost 4 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#4 Updated by Stephen Benjamin almost 4 years ago

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

Also available in: Atom PDF