Bug #9895

user can't vew discovery_rules with "Discovery Reader" role

Added by Ori Rabin over 2 years ago. Updated over 1 year ago.

Status:Closed
Priority:Normal
Assigned To:Ori Rabin
Category:Discovery plugin
Target version:Plugin 2.0.3
Difficulty: Pull request:https://github.com/theforeman/foreman_discovery/pull/173
Bugzilla link:1202294
Story points-
Velocity based estimate-

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1202294
Description of problem:
I created a user and assigned "discovery Reader" role to it. When login with created user, I can see the discovered host but not the discovery_rule.

Version-Release number of selected component (if applicable):
sat6.1 beta snap6 compose2 (Satellite-6.1.0-RHEL-6-20150311.1).

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:
can see the discovered host but not the discovery_rule with normal user

Expected results:
discovery rule should be viewable on login with normal user and when "discovery reader role is assigned to normal user

Additional info:


Related issues

Related to Foreman - Bug #13529: Duplicate permissions are allowed and not recognized Closed 02/02/2016

Associated revisions

Revision 0d9cee21
Added by Ori Rabin about 2 years ago

Fixes #9895 - user in Discovery Reader role should see discovery rules

Revision e51a7475
Added by Ori Rabin about 2 years ago

Refs #9895 - fixing resource type in discovery_rules permissions

History

#1 Updated by Ori Rabin over 2 years ago

  • Project changed from Foreman to Discovery
  • Category set to Discovery plugin
  • Status changed from New to Assigned

#2 Updated by The Foreman Bot over 2 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman_discovery/pull/173 added

#3 Updated by Lukas Zapletal over 2 years ago

  • Target version set to Plugin 2.0.3

#4 Updated by Ori Rabin about 2 years ago

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

#5 Updated by Lukas Zapletal about 2 years ago

  • Status changed from Closed to Assigned

This was NOT fixed properly.

#6 Updated by The Foreman Bot about 2 years ago

  • Status changed from Assigned to Ready For Testing

#7 Updated by Lukas Zapletal over 1 year ago

  • Status changed from Ready For Testing to Closed

Bot missed this one I guess.

#8 Updated by Lukas Zapletal about 1 year ago

  • Related to Bug #13529: Duplicate permissions are allowed and not recognized added

Also available in: Atom PDF