New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting limited access to Script Library causes problems #592

Closed
AdamNaj opened this Issue Feb 29, 2016 · 1 comment

Comments

Projects
None yet
1 participant
@AdamNaj
Member

AdamNaj commented Feb 29, 2016

Setting limited access to Script Library causes problems when any integration point is accessed by unprivileged user first. Such user will not have access to any script in the library and the cache will be populated as empty in the context of this user.

This "poisoned" cache will then persist for until any script is saved, which will invalidate the cache and cause it to be rebuilt the next time an integration point is accessed again. should it then be accessed by a privileged user all is fine but otherwise the problem persists.

"Accessing integration point" can constitute an event as trivial as right-click for context menu in Content Editor or loading a page in Experience/Page Editor (at which point Experience Editor Notification Integration Point is attempted to be accessed)

@AdamNaj AdamNaj self-assigned this Feb 29, 2016

@AdamNaj AdamNaj added this to the 4.0 milestone Feb 29, 2016

@AdamNaj

This comment has been minimized.

Member

AdamNaj commented Feb 29, 2016

Fixed.

@AdamNaj AdamNaj closed this Feb 29, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment