-
Notifications
You must be signed in to change notification settings - Fork 14
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
Redesign the permission management for project creation #127
Comments
I have a little doubt about this: as for now, the administrator grants the Will the user be able to directly create projects after this first approval & project creation by the admin ( this means to keep the permission system almost "as it is" already ) or is it intended that the user has to ask for every project creation ( more interferences for the IM or admin )? I guess this change is only meant for the first time, to ease the admin work and then leave the user the right to do by itself. Right? |
Done. The approval/deny of each project will be automatically made when the admin user ticks the corresponding check box. User shall go through this procedure every time he/she wants to request a project, as usual (although it is not the idea used for the permissions granting in the original Stanford's Expedient, which granted the The permission & permission management views, along with templates like the permission & confirmation requests were modified. Some are shown, to illustrate the changes and for future reference or whatsoever. File: expedient/src/python/expedient/clearinghouse/permissionmgmt/views.py
File: expedient/src/templates/default/expedient/clearinghouse/permissionmgmt/confirm_requests.html
File: expedient/src/templates/default/expedient/clearinghouse/permissionmgmt/request_permission.html
|
Project creation was modified because there were problems when project already existed. File: expedient/src/python/expedient/clearinghouse/permissionmgmt/views.py
|
Automatic project creation (in file expedient/src/python/expedient/clearinghouse/permissionmgmt/views.py) missed a
right after the
method is invoked; in order to link all this LDAP info properly. Otherwise the owner won't be able to access VMs via SSH (because he/she is not permitted in the LDAP's project section). Only when another user is added to the project (and therefore the project instance is saved), will he/she be able to access VMs... And yet another detail to be taken care of in the future (not an issue, though; but this will remain open) is that code is duplicated with this. It might be good to directly call
from the project views (file expedient/src/python/expedient/clearinghouse/project/views.py) and appropriately forge the currently existing request for permissions with the missing fields that the project form ( |
… (save project after granting roles to sync LDAP)
Modify the permission management of project request in the dashboard to let it create the project automatically with the data sent by the user.
The text was updated successfully, but these errors were encountered: