Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Add back SecurityService cache

Description

In the SecurityService cache got accidentally removed, spotted this (thanks) and it needs putting back. This was just an accidental refactor on my part and should not have been removed.

Activity

Show:

Matthew Buckett April 4, 2016 at 4:27 AM

Thanks, that's good, there's shouldn't be any difference in behaviour as all this does is make the performance good again.

Trisha Gordon March 24, 2016 at 10:51 AM

Matthew, I could not replicate this issue on https://qa11-mysql.nightly.sakaiproject.org/portal or https://trunk-mysql.nightly.sakaiproject.org/portal by following the steps you included in an earlier comment.

I tested using 2 accounts and giving permission in Announcements to create/delete own/edit own/ to the account with access role and refreshing the tool for that account and got the new capabilities promptly in both environments.

Could there be some step that I am missing? Or is this just fixed in both environments?

Matthew Buckett March 17, 2016 at 7:46 AM

It shouldn't matter which tool. Just check that permission changes are updated.

Neal Caidin March 17, 2016 at 7:42 AM

Any tool and any permission?

Matthew Buckett March 17, 2016 at 7:00 AM

Have 2 users logged into Sakai at the same time, check that when changing permissions all that is needed for the other user to see the changes is to reset the tool.

Fixed

Details

Priority

Affects versions

Fix versions

Components

Assignee

Reporter

Labels

Created February 23, 2016 at 3:35 AM
Updated April 25, 2018 at 3:18 PM
Resolved March 1, 2016 at 9:56 AM