• We value your experience with Plesk during 2025
    Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025.
    Please take this short survey:

    https://survey.webpros.com/
  • On Plesk for Linux mod_status is disabled on upgrades to improve Apache security.
    This is a one-time operation that occurs during an upgrade. You can manually enable mod_status later if needed.

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