Submitted by masterg0g0 on Mon, 08/06/2018 - 02:30 Pro Licensee
Hi There,
So along with virtualmin DB management gui interface, i am also wanting to give my customers.. management via phpMyAdmin. Can you help here? basically i have configuring phpMyAdmin at the localhost, and created a menu link for my customers so that they dont have to install phpMyAdmin and i can allow all Virtualmin domain to access their db via this menu link i have created.
Now the problem is that via phpMyAdmin, the privileges are missing for new DBs to be created... as shown. https://d.pr/i/ukFiuS
How can fix this so that the behavior inside phpMyAdmin is similar to that of from the virtualmin GUI for a particular domain user.
Thanks, Rohit
Status:
Closed (works as designed)
Comments
Submitted by andreychek on Mon, 08/06/2018 - 10:18 Comment #1
Howdy -- thanks for contacting us!
I unfortunately don't believe that would work.
That is, there is no way to add/remove databases using outside tools in a way that would have it associated with the user in question.
That is, you can certainly make it so that a user can create a database -- but if they do, Virtualmin won't know anything about it, it wouldn't be associated with that user's account, and perhaps most importantly it won't be included in the Virtualmin backups.
My suggestion instead is to use Virtualmin for creating databases, but allow users to use phpMyAdmin to manage any existing databases. Would that work?
Submitted by masterg0g0 on Tue, 08/07/2018 - 03:06 Pro Licensee Comment #2
Hi ,
I am already doing what you suggested, Could you discuss this with Jamie/Joe .. what is different for the admin db user in terms of authorization.. the same user is able to create new DB from the virtualmin GUI and this user has no privileges inside of phpmyadmin?
Submitted by andreychek on Tue, 08/07/2018 - 06:45 Comment #3
When using Virtualmin to create a database, it's not your database user that's creating the new database -- it's actually Virtualmin creating the database using the root MySQL user.
When that happens, Virtualmin also adds the database name to that particular Virtual Server's metadata, so that Virtualmin knows it's owned by that user, and Virtualmin will also include it with the backups.
It's possible to modify a user so that it can create databases outside of Virtualmin.
But, if you do so, those databases wouldn't be associated with any given Virtual Server in Virtualmin, and won't be included in the backups.
Because of those issues, we unfortunately can't recommend that.... Virtualmin really is designed to create the databases itself, rather than have databases created by a third party tool.
Submitted by masterg0g0 on Tue, 08/07/2018 - 06:51 Pro Licensee Comment #4
Ok thanks for your clarification, this helps. I have closed the ticket