Manage MySQL Users in Navicat Premium | Part 2: Create New Users

Part 2: Create a new user

Part 2: Create a New User In Part 1 , we learned how to protect the MySQL root account using the Navicat Premium user management tool. This article will focus on setting up account details, account restrictions, and SSL settings for new users. If you want to learn while using? Click here to download a 14-day free full-featured trial version.

"General" tab

Clicking the New User button on the object toolbar will open the untitled Users tab. It contains five tabs, namely "General", "Advanced", "Server Privileges", "Permissions" and "SQL Preview". We already covered the General tab in Part 1, but we'll do a quick recap here. On the General tab we need to provide:

" Username "
The database " host "
Encryption " plugins". Select "mysql_native_password" or "sha256_password" from the dropdown list
" Password "
" Password Expiration Policy "

Setting Password Policy
MySQL allows database administrators to manually set account password expiration, and use the MySQL mysql_native_password or sha256_password built-in authentication plug-in to establish an automatic password expiration strategy.
Navicat provides several options via a drop-down list, summarizing the common MySQL mechanism for setting password expiration using the PASSWORD EXPIRE statement. they are:

DEFAULT: Sets the password expiration time length to the default value of the database. Prior to version 5.7.11, the default was 360 days. As of version 5.7.11, the default is 0 days, which effectively disables automatic password expiration.
IMMEDIATE: Expires the account password, forcing the user to update it.
INTERVAL: Specifies the number of days after which the current password expires.
NEVER: Allows the current password to remain valid indefinitely. Useful for scripts and other automated processes.

Here is an example:

"Advanced" tab

You can find account restrictions and SSL settings here.

Account restrictions
MySQL allows personal accounts to be limited to use various server resources to avoid any one user monopolizing resources. Restrictions include:

The number of queries an account can issue per hour.
The number of updates an account can issue per hour.
The number of times an account can connect to the server per hour.
The total number of servers an account can connect to.

These are equivalent to the fields in the Advanced tab: " Maximum queries per hour ", " Maximum updates per hour ", " Maximum connections per hour " and " Maximum user connections ". Each of these fields accepts a value of zero (0) or a positive integer.

SSL Setup
To use encrypted connections, OpenSSL or yaSSL must be present on the system. Additionally, the MySQL server needs to be built with TLS support and properly configured to use either OpenSSL or yaSSL. Note that the term SSL refers to the older, now insecure protocol prior to TLS. Although MySQL only uses its more secure (TLS) successor protocol, it is still used in many variable names and options for compatibility reasons.

The SSL Type drop-down field maps to the ssl_type column of the mysql.user table, which only accepts certain values: ANY, SPECIFIED, and X509 (and '' for NONE).

Additionally, the MySQL GRANT statement accepts ISSUER, SUBJECT, and CIPHER options. These options can be combined in any order, and REQUIRE X509 is implicit if you use any of them.
Here is a GRANT statement followed by the equivalent Navicat "Advanced" tab:
GRANT USAGE ON *.* TO 'bob_s'@'localhost' REQUIRE SUBJECT '/CN= http://www.mydom.com/O= My Dom, Inc./C=US/ST=Oregon/L=Portland' AND ISSUER '/C=FI/ST=Somewhere/L=City/ O=Some Company/CN=Peter Parker/emailAddress= p.parker@ marvel.com ' AND CIPHER 'SHA-DES-CBC3-EDH-RSA';

notice

In Part 3, we'll move on to the last three user tabs. If you want to learn while using? Click here to download a 14-day free full-featured trial version.