• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Question granular scope permissions for Plesk REST API

burnley

burnley

Regular Pleskian
Lately we have had a lot of clients and their technical providers that have started using the Plesk REST API to implement DNS based validation for SSL certificate automation projects. At present they can generate an API Key at the client level which is locked down via IP.

The issue is many have asked how to restrict the key so its only usable for a specific domain or sub-domain in their account as they need to provide access for a 3rd party to validate certificates on externally managed infrastructure. Several have also pointed out the key grants all client level permissions. There seems to be no way to limit a KEY to DNS only related commands or even more tightly ones related specifically to verification records for SSL certificates.

So far the only solution seems to be to use an external provider such as Cloudflare. Is this something Plesk is looking at addressing in a future release or did I overlook something in the REST API. Has anyone else found a good solution using Plesk?
 
Hi, @burnley . At this point, there are no initiatives for changes in the API keys scope. Your use-case sounds valid and I believe our team will be interested in exploring it further. Could you please submit a request on feature.plesk.com and provide as many details as possible?
 
Not a problem, a feature' request has been submitted as 'Granular scope permissions for Plesk API' Hopefully its something they will consider while there are a lot of these integration projects being done. Once these projects are setup with other methods they are unlikely to want to use Plesk DNS again.
 
You must log in or register to reply here.

Similar threads

T
Input [Feature Request] Add php_handler_id to Plesk Rest API [GET] /domains
Replies
4
Views
5K
Sebahat.hadzhi
Sebahat.hadzhi
Azurel
Question ACME SSL: How to configure DNS-01 with external DNS provider?
Replies
6
Views
5K
Sebahat.hadzhi
Sebahat.hadzhi
T
Question How to update the DNS resolvable verifications through REST API?
Replies
3
Views
4K
tertek
T
A
Question Automate the migration process between Plesk servers using the XML/REST API
Replies
0
Views
2K
AndreyKashin
A
D
Forwarded to devs SSL It! / Let's Encrypt DNS-01 challenge remains permanently "Pending" – TXT records created successfully but challenge is never confirmed
Replies
3
Views
5K
Sebahat.hadzhi
Sebahat.hadzhi
Back
Top