icingaweb2 icon indicating copy to clipboard operation
icingaweb2 copied to clipboard

Changing permissions requires that all users log out and in again

Open mphilipps opened this issue 7 years ago • 5 comments

hi,

Expected Behavior

When I change a role's permissions or filters they should immediate be applied the next request for the affected users.

Current Behavior

Currently the user needs to logout and log in again to reload his permissions.

Steps to Reproduce (for bugs)

  1. Create a role like this:
[test_role]
users = "user1"
permissions = "module/monitoring, monitoring/command/schedule-check"
  1. Let the user login, note that he can't see an hosts/services
  2. Amend the config with monitoring/filter/objects = "host_name=icinga-client.example.com"
  3. Not that even after hitting F5 user1 still can't see the icinga-client.
  4. Logout user1 and log in again and he suddenly can see the icinga-client.

Context

This is even worse if you want to remove someone's permission. If the user doesn't log gout he can still see the machines/check results and even schedule new checks.

Your Environment

  • Icinga Web 2 version and modules (System - About): 2.6.1
  • Version used (icinga2 --version): 2.9.1-1
  • Operating System and version: Debian stretch
  • Enabled features (icinga2 feature list): api checker command ido-pgsql mainlog notification
  • Config validation (icinga2 daemon -C): valid

mphilipps avatar Aug 09 '18 14:08 mphilipps

+1

bunghi avatar Sep 10 '18 09:09 bunghi

Hi,

Thanks for the report. We consider this feature for one of our next releases but there's no exact schedule yet.

Best, Eric

lippserd avatar Nov 16 '18 14:11 lippserd

Thanks, but how is this considered a feature? Logged in users keeping there permissions indefinitely is intended?

The ideal solution and this I would agree is a feature/enhancement would be for each user to have their own api user.

mphilipps avatar Nov 16 '18 15:11 mphilipps

ref/NC/775781

tbauriedel avatar Feb 06 '23 12:02 tbauriedel

Sounds like

  • #3391

would be an alternative if it can also forcibly log out users.

Al2Klimov avatar Oct 04 '23 13:10 Al2Klimov