• 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 Using a server wide, customizable prefix for MySQL db name and db user

burnley

Regular Pleskian
Hi,

Loosely related to the previous thread. I'm trying to find secure ways to integrate Plesk with a MySQL cluster and I'm hitting a major roadblock: Plesk appears to take over the remote MySQL instance, it requires an user with all privileges + grant option and this is fine, but I'd like to limit the scope of what this Plesk DB user can access. E.g. I'd like to know whether it's possible to only limit the Plesk user's access to databases on the remote server that have a predefined prefix, e.g. 'psk_'. Right out of the box it doesn't seem to be possible at the moment, since Plesk tests its ability to use the remote MySQL server by attempting create a database with a random name which I can't control.
I wouldn't mind having to use a global server variable in /etc/psa/psa.conf like:
# MySQL
[...]
MYSQL_DBNAME_PREFIX psk
MYSQL_DBUSER_PREFIX psk

Any ideas?
 
Back
Top