Regular Webmin users need to be able create, edit and delete virtual servers. At the same time it gets messy when they start playing with system settings.
I didn't want the regular Webmin users to be able to change important Virtualmin's system settings, so set "No" for the "Can edit module configuration?" option on the "Virtualmin Virtual Servers access control options" page (Webmin). That hid the "System Settings" block for a regular Webmin user (desired effect), however it also made Delete and Disable functions not available giving the:
You are not allowed to edit this virtual server
error. So first of all the wording of the message above is not correct since clicking on the "Edit virtual server" link shows all the options available. Secondly, I believe Delete and Disable functions are incorrectly bound to "Edit module configuration" permissions. I believe they should be in the same group with "Create virtual server" and "Edit virtual server" since Deleting or Disabling a virtual server has nothing with configuring Virtualmin's settings.
Edit: Seems not only Delete and Disable, but also several other features related to virtual servers are incorrectly associated with Virtualmin's system settings like:
Limits and Validation
Backup and Restore
Fortunately, two other features - Import or Migrate and List Virtual Servers pertaining to virtual servers are still there.
I agree that the following features:
System Settings
Email Messages
System Customization
Addresses and Networking
are indeed system settings (since you can configure things there) and should be hidden when the "Can edit module configuration?" option is set to "No", however:
Limits and Validation
Backup and Restore
are not configuration sections, they are functions directly related to virtual servers, so should stay available to Webmin users who can create virtual servers. Please consider this request to decouple virtual servers related functions from configuration sections.
Comments
Submitted by yngens on Fri, 02/12/2016 - 04:58 Comment #1
Submitted by yngens on Fri, 02/12/2016 - 05:21 Comment #2
Submitted by yngens on Fri, 02/12/2016 - 05:22 Comment #3
Added additional text to the body of the text above.
Submitted by yngens on Fri, 02/12/2016 - 05:23 Comment #4
Submitted by JamieCameron on Fri, 02/12/2016 - 23:06 Comment #5
Can you tell me more about what you're trying to setup here? Are you looking to create a virtualmin user who can create, edit and delete any domain, but cannot edit global settings?
Submitted by yngens on Sun, 02/14/2016 - 17:17 Comment #6
Can you tell me more about what you're trying to setup here? Are you looking to create a virtualmin user who can create, edit and delete any domain, but cannot edit global settings?
Yes, I'd like to create a Virtualmin user (which in fact a Webmin user as I understand) that is able to only manage everything that pertains the accosicated (with it) virtual server and that is not able to change any global settings for the system (Virtualmin, Webmin). It makes much sense to me to keep all the functionality features for virtual servers separate from configuration settings.
Submitted by JamieCameron on Sun, 02/14/2016 - 20:57 Comment #7
Yes, I'd like to create a Virtualmin user (which in fact a Webmin user as I understand) that is able to only manage everything that pertains the accosicated (with it) virtual serverBut that's what a Webmin user created by Virtualmin is limited to be default (other than the deletion of top-level domains)?
Submitted by yngens on Mon, 02/15/2016 - 23:41 Comment #8
Right, but why a Webmin user can create a domain and can not delete it? Why deletion function and also Limits and Validation, Backup and Restore (functions!) should be associated with Virtualmins system (configuration!) settings? It really would make much sense to de-couple all functions from configurations.
I believe if one is allowed to create virtual server (domain) then he should be able to edit, validate, backup, restore and delete it. And this should have nothing with Virtualmin's system configuration settings.
Submitted by yngens on Fri, 04/22/2016 - 23:48 Comment #9
Any updates on this? Jamie, please run some tests - it really doesn't make sense to mix up features (functions) with configurations. And then if you allow someone to create a virtual server then s/he should be able to also edit, backup, delete or anything with it.
Submitted by yngens on Sat, 10/22/2016 - 01:24 Comment #10
Ok, forget about deleting the top level domain. But why really Webmin users can not enjoy using the Limits and Validation, Backup and Restore features?
Submitted by yngens on Wed, 11/02/2016 - 14:39 Comment #11
Somehow "Backup and Restore" feature was made available to Webmin users (though not without issues as discussed on https://www.virtualmin.com/node/43282), which is already good. So now, what about "Limits and Validation" feature? Why Webmin users should not be able to validate their websites to identify configuration issues?
Submitted by JamieCameron on Wed, 11/02/2016 - 23:33 Comment #12
Can you clarify what you mean by "Webmin user" ? Do you mean the Webmin login associated with a top-level virtual server?
Submitted by yngens on Thu, 11/03/2016 - 01:08 Comment #13
Yep, the user that has Webmin login right. S/he can now use "Backup and Restore" feature, but can not use "Limits and Validation" feature.
Submitted by JamieCameron on Thu, 11/03/2016 - 23:21 Comment #14
Ok, I'll look into adding this
Submitted by JamieCameron on Tue, 11/08/2016 - 10:45 Comment #15
This has been implemented - an option to allow domain owners to perform validation will be included in the next (5.05) Virtualmin release.
Submitted by JamieCameron on Tue, 11/08/2016 - 10:45 Comment #16