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

Probs with MySQL databases

C

colinjack

Guest
Couple of issues with clients using MySQL through the Plesk interface:

1. You can set up separate databases, but can't allocate access etc to pre-existing users. DB Users seem to be allocated on a per database basis which seems counter intuitive. This is a real pain as it means you can't use separate databases for different tasks. It would be much nicer if there was a mechanism that allowed you to provide access and privileges to particular current users.

2. No info on priveleges/permissions allocated to database users - It seems as though you can't modify whatever the default is via the control panel. This just seems daft. It means that you can't set up a user with restricted privileges in order to minimise security problems when it's publicly available. By default (only found via an SQL query in PHPMyAdmin), the user has 'SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, REFERENCES, INDEX, ALTER, LOCK' rights.

Any comments or workarounds appreciated.
 
Back
Top