[VOMS812] PERMISSION CACHE SHOULD BE CLEANED UP WHENEVER INTERESTING

[VOMS812] PERMISSION CACHE SHOULD BE CLEANED UP WHENEVER INTERESTING






[#VOMS-812] Permission cache should be cleaned up whenever interesting user related events are raised

[VOMS-812] Permission cache should be cleaned up whenever interesting user related events are raised Created: 21/Jun/17  Updated: 27/May/21  Resolved: 03/Aug/17

Status:

Closed

Project:

VOMS

Component/s:

admin-server

Affects Version/s:

VOMS Admin server v. 3.6.0

Fix Version/s:

VOMS Admin server v. 3.7.0

Security Level:

Public (Visbile by non-authn users.)


Type:

Bug

Priority:

Major

Reporter:

Andrea Ceccanti

Assignee:

Andrea Ceccanti

Resolution:

Fixed

Votes:

0

Labels:

None

Remaining Estimate:

Not Specified

Time Spent:

Not Specified

Original Estimate:

Not Specified



 Description 

 

In 3.6.0 a permission cache mechanism was introduced to improve VOMS Admin responsiveness.
A mechanism was put in place to clean up the cache whenever an ACL update event was raised. This was insufficient to ensure that the cache wouldn't be
"transparent", as permission for an authenticated user are not only derived from ACLs but from user Role and group membership as well.

So the permission cache should be cleaned up whenever an "interesting" user related event is raised internally in VOMS Admin, e.g. when users are created/deleted, when group membership changes, when roles are assigned/dismissed.


Generated at Mon Mar 07 23:16:49 CET 2022 using Jira 8.20.3#820003-sha1:e9c1f3b400a5545d56ec3d8e0414de7a0e75ddb3.





Tags: cache should, permission cache, cleaned, should, [voms812], permission, whenever, cache, interesting