-
Notifications
You must be signed in to change notification settings - Fork 3
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
Allow for mulit-user setup #22
Comments
As early stage of development we are trying to first finalize a working prototype where is possible to:
the prototype will work in a single user setup. Of course the plan for There are different possibilities to handle multiuser, like:
This is the direction, but unfortunately will take a while before we can handle multiuser access, for now the focus is on the single user app. btw, @ninsbl thanks a lot for testing and for valuable feedback! |
Thank for clarification! Looking forward to a working prototype which can be used for showcasing the potential of your "early stage of development work". |
Currently WebGRASS is compiled for, and run as one specific user.
In multi-user environments with multi-user GRASS DBs, that causes (or at least can cause) severe problems for data security/integrity (users might work in mapsets in parallel for example). Also there would be no way to distinguish access rights for mapsets for different users if all are treated as the same. Finally, when a console will be added in future, all users will be able to see and modify all other user`s data...
Thus a multi-user setup (where logins are mapped to system users) will be quite essential for usage esp. in enterprise settings.
I understand, this is likely also a more longterm development related to #19...
The text was updated successfully, but these errors were encountered: