Skip to content
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

security error doing senders as non-SystemUser user ... #52

Open
dalehenrich opened this issue May 9, 2017 · 3 comments
Open

security error doing senders as non-SystemUser user ... #52

dalehenrich opened this issue May 9, 2017 · 3 comments

Comments

@dalehenrich
Copy link
Contributor

Logging in as DataCurator or another non-SystemUser user is a common use case. In these cases though, shared globals owned by SystemUser can be problematic unless one either adjusts the permissions on the shared global or puts user-specific globals into UserGlobals (which exists on a per-user basis) or puts user-specific globals into Session Temps ...

In this case it looks like you are already using SessionTemps for the cached class organizer, so it probably makes sense to cache your default GtGsSystemNavigation instance in session temps as well ...

screen shot 2017-05-09 at 6 19 22 am

@dalehenrich
Copy link
Contributor Author

... a fourth option is to initial the shared global at load time thus creating the instance as SystemUser ...

@dalehenrich
Copy link
Contributor Author

in this particular case it looks like forcing the initialization of the global at load time will work ... I logged in as SystemUser, initialized the global, and senders/implementors now works for DataCurator ...

chisandrei added a commit that referenced this issue May 9, 2017
@chisandrei
Copy link
Member

Forgot that lazy initialization of shared data can be an issue. Changed the code to use SessionTemps instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants