MySQL as a Data Source

avatar
999
Disabled

I apologize if this is redundant, but the only other topics I could find are quite old. I setup a MySQL (MariaDB) database to use as a data source. Everything worked OK. Both 'Test Host' and 'Test Schema' reported successful. However, once I started using the data source, I realized it was set to read only. I could not add connection entries, folders, etc. I looked through the forums, as well as Google, but could only find old topics that did not work in my scenario.

Any assistance is appreciated. I am using Remote Desktop Manager Enterprise version 2020.2.20.0 64-bit.

Thank you.

All Comments (2)

avatar

Hello,

Are you able to connect using the root account via the File -> DataSource menu? If yes, I would recommend connecting with this account and then, create your first admin account via the Administration -> Users. By doing this, your first administrator should ge the proper privileges on the database.

Best regards,

Jeff Dagenais

avatar

Thank you. Unfortunately, if you use root at the start, it makes root the definer of the database procedures, and you have to keep using it. As using root (especially remotely is a security risk, I needed to use a separate username. After some Googling and starting over, here is what works - hoping this helps someone else:

1)Create a user with equivalent of root privileges (make sure to use the percent, as it is a wild card)

create user 'user1'@'%' IDENTIFIED BY 'password1';
GRANT ALL PRIVILEGES ON *.* TO 'user1'@'%' WITH GRANT OPTION;
flush privileges;


2) Create database

CREATE DATABASE rdmdatabase;


3) Use this database and username/password combination inside Remote Desktop Manager. It will create the tables and permissions properly now.

4) Remove root permisions from the user, and add access to the database.

revoke all privileges, grant option from 'user1';
GRANT ALL PRIVILEGES ON rdmdatabase.* TO 'user1'@'%';


Now, this will have the side effect of not being to add separate users to the database. I think it would work best in a dedicated database model. But it cuts out the security risks.

Closed