Home » Mysql » Re-assign host access permission to MySQL user

Re-assign host access permission to MySQL user

Posted by: admin November 1, 2017 Leave a comment


I have several thousand MySQL users all set to allow access from a specific host. The problem is that now I’m going to have two machines (more in the future) which will need to use the same account to access each of their databases.

I’d like a quick and easy (as automated as possible) way to run through and modify the host portion of each user account to fit an internal network wildcard. For example:

‘bugsy’@’internalfoo’ has access to the ‘bugsy’ DB.

I want to now allow bugsy access from anywhere on the internal network

‘bugsy’@’10.0.0.%’ has access to the ‘bugsy’ DB.


For reference, the solution is:

UPDATE mysql.user SET host = '10.0.0.%' WHERE host = 'internalfoo' AND user != 'root';
UPDATE mysql.db SET host = '10.0.0.%' WHERE host = 'internalfoo' AND user != 'root';


The accepted answer only renamed the user but the privileges were left behind.

I’d recommend using:

RENAME USER 'foo'@'' TO 'foo'@'';

According to MySQL documentation:

RENAME USER causes the privileges held by the old user to be those held by the new user.


The more general answer is

UPDATE mysql.user SET host = {newhost} WHERE user = {youruser}


I haven’t had to do this, so take this with a grain of salt and a big helping of “test, test, test”.

What happens if (in a safe controlled test environment) you directly modify the Host column in the mysql.user and probably mysql.db tables? (E.g., with an update statement.) I don’t think MySQL uses the user’s host as part of the password encoding (the PASSWORD function doesn’t suggest it does), but you’ll have to try it to be sure. You may need to issue a FLUSH PRIVILEGES command (or stop and restart the server).

For some storage engines (MyISAM, for instance), you may also need to check/modify the .frm file any views that user has created. The .frm file stores the definer, including the definer’s host. (I have had to do this, when moving databases between hosts where there had been a misconfiguration causing the wrong host to be recorded…)