• 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.

API-RPC create alias by client. Fixed?

J

Johand

Guest
We're building a webservice which needs the ability to add domain aliasses under an existing domain. To do this we've made a PHP class which connects to the Plesk API to make the changes in Plesk.

To keep it as secure as possible we want to use a client to login to the API instead of the administrator, but a client (or reseller) has no permission to work with aliasses.

At the knowledgebase we've found a hotfix for this problem (http://kb.odin.com/7075), which works without a problem.

Now the big question: At the moment we're using Plesk 9.3, and the latest version is 9.5 but at the changelog there is no comment about this problem. So, is the hotfix committed in the latest version? Or do we have to mannually apply the fix again when we update?
 
Back
Top