yahoo-eng-team team mailing list archive

[Thiago Paiva Brito <thiagop@xxxxxxxxxxxxxxx>]

@Timur: I tested it and happened that my panel has been disabled. But I
had to log out and restart Horizon so it can update the policy that was
already in memory. There is a double problem here:

1) Horizon isn't considering policy changes until restart

2) Permissions are persistent while the session is opened

** Changed in: horizon
       Status: New => Opinion

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1379358

Title:
  Attribute `policy_rules` of a Panel instance is not considered while
  determining the Panel visibility

Status in OpenStack Dashboard (Horizon):
  Opinion

Bug description:
  The Panel class is a subclass of HorizonComponent class, which should
  check `self.policy_rules` while determining whether the entity is
  visible or not. It isn't the case for Identity -> Users panel
  https://github.com/openstack/horizon/blob/2014.2.rc1/openstack_dashboard/dashboards/identity/users/panel.py#L29
  You can check it yourself by changing both rules in
  https://github.com/openstack/horizon/blob/2014.2.rc1/openstack_dashboard/conf/keystone_policy.json#L43
  to "!" and see that the panel is still visible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1379358/+subscriptions