• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

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