• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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