Change password db-user

[firewolf]

In the cpanel mysql-databases there is no script for changing the password of db-users. I suppose it can be done with a sql-query. But before you do that, you must be very sure that the syntax is correct.

[GvilleRick]

In the past when I have needed to change the password of the db-user I would just delete the user in the cPanel Database section and then add it back with the new password.

[firewolf]

I have considered that option. But the db-user I want to change the password from, has access to several databases. And I like to change the password every month. It would be a lot of work each month to set the rights for this user for every database.

[GvilleRick]

It would be a lot of work and if the password is stored in a connection file that would need to be changed as well. In any case, for a feature to be added to cpanel you should make the suggestion to cPanel at cPanel.net. HG doesn't have control over the cPanel options.

[GatorCarl]

You don't need to erase the user first. You can reset the password by just putting in the same username and a different password. This will leave the permissions on the specific databases as well.

[firewolf]

I have tried the suggestion of GatorCarl
and it works fine.
Thanks !

[fredheitmann]

Originally Posted by GatorCarl

You don't need to erase the user first. You can reset the password by just putting in the same username and a different password. This will leave the permissions on the specific databases as well.

Where exactly I should do this? I have tried it on "MySQL Databases" but got a response like this:

"That mysql username is taken"

[GatorCarl]

This did work previously but it looks like with the 11.28 update, the username needs to be removed first and then re-added with the new password.

[virtvir5]

Part of cPanel 11.28's marvellous "improvements" to eliminate its former insistence on dB name and username prefixes, no doubt.

Perhaps someone should pass this one along to cPanelDavid too. But I'm not sure there's anything they can actually do about it given the inevitable consequences of that underlying decision to allow dB names with no distinguishing prefixes on shared servers.