top of page

MySQL create multiple accounts for an application

You can now grant CREATE USER so that your apps would be talented to use several accounts without you exposing the end user takeover the database by altering your root credentials for case. Wouldn’t it be good, if you could allow a user privileges to create or change users excluding a few users? If you have such use cases, then this blog post will notice you.

First, let us realize how you can modify a user’s provisions. There are subsequent two ways to do that.

  • Using a DDL queries if you have ‘CREATE USER’ privilege.

For example:

Now, foo can do the following:

  • Through a DML statements if you have DB-level privileges on the mysql database.

For example:

Now, foo can do the following:

In individually cases, foo was able to change the root account. What if you want to shield accounts such as root from being changed by other users?

In MySQL 8, we have additional the subsequent two capabilities.

A SYSTEM_USER rights. It stops users who have that rights from being changed by the users who have rights to create or modify users, but do not have the SYSTEM_USER rights. You can read more about SYSTEM_USER in this blog.

Revoke rights from database objects, even if the user is approved global rights. You can read more about rights limitations in this blog.

This blog shows how to keep users leveraging the preceding two competences. Let us realize doing that over the subsequent example.

The debate here adopts that ‘partial_revokes’ system variable is ON.

We produce two users and grant the CREATE USER rights to them.

Grant the SYSTEM_USER privilege to one user.

Grant the global update rights to other user, but revoke rights on the mysql database.

bar_admin cannot alter foo_admin using DDL declarations because foo_admin has SYSTEM_USER but bar_admin does not.

bar_admin cannot change foo_admin because rights on the mysql database have been canceled.

So, you created a user ‘foo_admin’ who cannot be altered by another user even though the final has rights to alter some users. For bar_admin to alter foo_admin, bar_admin essential also have the SYSTEM_USER rights.

Let us generate additional user who has ‘CREATE USER’ and ‘SYSTEM_USER’ rights. This user can alter the properties of user ‘foo_admin’.

baz_admin can change the password of foo_admin.

As we motto, to modify the properties of a user who is approved the SYSTEM_USER rights, you need to have CREATE USER as well as SYSTEM_USER rights.

Based on the previous explanations, we may imagine users with respect to the SYSTEM_USER and CREATE USER rights

System Users:

Users who are fixed at least ‘SYSTEM_USER’ rights, but not the CREATE USER rights. These users themselves have no ability to change other users. These users can only be altered by power users.

Privileged Users

The users who are fixed at least ‘CREATE USER’ rights, but not the ‘SYSTEM_USER’ rights. These users can alter the all users excluding system users.

Non-privileged Users

The users who have neither ‘SYSTEM_USER’ nor ‘CREATE USER’ rights but may be settled other rights. These users cannot change any other users.

Power Users:

The users who are settled at least the ‘SYSTEM_USER’ and ‘CREATE USER’ rights. These users can change any user existing in the database. These users are most influential users henceforth named as power users.

The plan to create the unchallenged users

  • Assess cautiously which users need to be approved the SYSTEM_USER rights. There should not be several users who will need the SYSTEM_USER rights.

  • To keep users against being altered through DDL queries, grant them the SYSTEM_USER rights. This avoids them from being changed by users who do not have SYSTEM_USER. Your root account will be one of them. Not unexpectedly, it is fixed the SYSTEM_USER treat by default.

  • To keep against being changed through DML queries, enforce a limited revoke on the mysql database on administrative users. First, you may produce an administrative user who has DB-related rights, granted altogether but canceled for mysql database. You may use this administrative user to grant rights to other users. You could attain the same result through roles and creating them default as well. Whatever suits your utmost ?

Let us see how to do that over a role.

Create an administrator user who needs the total access of DB-level rights. We can accomplish this by granting the earlier created role to the user.

Connect as the administrator and initiate the role to get the essential rights.


In this post we cultured to create users who are can be protected from getting changed by the users who typically create and modify users.

We expectation you found this post useful. Please give the methods defined here a try.

Thank you for using MySQL:)

10 views0 comments

Recent Posts

See All

What are the future prospects of Java

According to a survey conducted, nearly 63% programmers mentioned that they will likely continue to work with Java along with coding with Python, SQL and HTML/CSS. In addition, the giants in the corpo

Deleting Duplicate Rows in MySQL

In this blog, you will study several ways to delete duplicate rows in MySQL. In this blog, I have shown you how to find duplicate values in a table. Once the duplicates rows are recognized, you may ne

Upload Data to MySQL tables using mysqlimport

Uploading quite a lot of rows of data from a text, csv, and excel file into a MySQL table is a repetitive task for sysadmins and DBAs who are handling MySQL database. This blog clarifies 4 applied exa


bottom of page