-
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
Enable per user-level #3
Comments
It is simple to disable it for users and resellers as an admin, but per reseller/per user is a bit harder. How should we store the option which user is allowed to use the plugin? In the user config of DirectAdmin itself or something like an ACL? |
This can actually be done for package or user. DirectAdmin has such option |
Good to know, thank you! |
But can you add this Lets encrypt plugin as a user setting or package? It's not about SSL itself. |
SSL needs to be enabled anyway to use this plugin. If da-letsencrypt=on for an user, but the SSL feature of DirectAdmin, the plugin will not be showed/usable. If da-letsencrypt=on and the SSL feature of DirectAdmin is enabled, the plugin will be shown. If da-letsencrypt=off and the SSL feature of DirectAdmin is enabled, the plugin will not be showed and not usable for that user. I will develop the functionality to enable/disable per package first. |
Hmm, didn't know it was possible to add an extra option to a package / user. Nice! That is really awesome :) |
Here is some info: There is also a good feature in the development now: |
The 479 is currently only for the sysadmins or the server owners itself, not for plugins unfortunately. 1617 seems really nice, but that's something we need to wait for indeed. Thx for the useful links! |
1617 seems the best option to wait for. Let's add a feature to enable/disable it for all resellers and/or all users for now in combination with the SSL feature of DA to have a little bit of control untill 1617 is ready. |
Modified milestone because we have to wait for it before it's available. |
Add functionality to enable or disable this plugin per user level.
For example: the admin does not want his users to request SSL certificates because of his sale model. He want's to disable the user level access.
This changes user=yes to user=no in plugin.conf
The text was updated successfully, but these errors were encountered: