Search Results
https://dev.mysql.com/doc/mysql-monitor/8.0/en/mem-agent-rights.html
During the installation process, you are prompted to create General and Limited users. You can allow the agent to connect to the database using the Admin user for all tasks but it is recommended to create the General or Limited users for tasks which ... MySQL Enterprise Monitor Agent requires a user configured within each MySQL instance that is being monitored with suitable privileges to collect information about the server, including variable names, replication, and storage engine status ...
https://dev.mysql.com/doc/mysql-secure-deployment-guide/8.0/en/secure-deployment-user-accounts.html
It demonstrates configuring global password policies, using security-related CREATE USER options, granting user privileges, and verifying user privileges and authentication. $> cd /usr/local/mysql $> bin/mysql -u root -p Enter password: (enter root ...The user1 account is defined with an SSL/TLS option that requires an encrypted ...Define global password history, reuse, expiration, and verification-required policies: A ...
https://dev.mysql.com/doc/refman/8.4/en/grant.html
Normally, a database administrator first uses CREATE USER to create an account and define its nonprivilege characteristics such as its password, whether it uses secure connections, and limits on access to server resources, then uses GRANT to define ...[WITH GRANT OPTION] [AS user [WITH ROLE DEFAULT | NONE | ALL | ALL EXCEPT role [, role ] ...These syntax ...
https://dev.mysql.com/doc/refman/8.4/en/pam-pluggable-authentication.html
To refer to the PAM authentication plugin in the IDENTIFIED WITH clause of a CREATE USER statement, use the name authentication_pam. For example: CREATE USER user IDENTIFIED WITH authentication_pam AS 'auth_string'; The authentication string ...
https://dev.mysql.com/doc/refman/8.4/en/privileges-provided.html
(The CREATE USER privilege also enables use of the CREATE ROLE statement.) See Section 8.2.10, “Using Roles”. The CREATE ROLE and DROP ROLE privileges are not as powerful as CREATE USER because they can be used only to create and drop accounts.
https://dev.mysql.com/doc/refman/8.4/en/password-management.html
To establish policy for individual accounts, use the PASSWORD EXPIRE option of the CREATE USER and ALTER USER statements. See Section 15.7.1.3, “CREATE USER Statement”, and Section 15.7.1.1, “ALTER USER Statement”. Example account-specific ...In that case, the server writes messages similar to these to the error log during the startup process (the exact numbers may vary): [ERROR] Column count of mysql.user is ...
https://dev.mysql.com/doc/refman/8.4/en/creating-accounts.html
To manage MySQL accounts, use the SQL statements intended for that purpose: CREATE USER and DROP USER create and remove accounts. These examples assume that the MySQL root account has the CREATE USER privilege and all privileges that it grants to ...Another option for creating accounts is to use the GUI tool MySQL ...
https://dev.mysql.com/doc/refman/8.4/en/replication-howto-repuser.html
Although you do not have to create an account specifically for replication, you should be aware that the replication user name and password are stored in plain text in the replica's connection metadata repository mysql.slave_master_info (see Section ... Each replica connects to the source using a MySQL user name and password, so there must be a user account on the source that the replica can use to ...
https://dev.mysql.com/doc/refman/8.4/en/create-table-foreign-keys.html
A duplicate symbol results in an error similar to: ERROR 1005 (HY000): Can't create table 'test.fk1' (errno: 121). NDB Cluster stores foreign key names using the same lettercase with which they are created. Creating a foreign key constraint requires ... MySQL supports foreign keys, which permit cross-referencing related data across tables, and foreign key constraints, which help keep the related data ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-backup-using-management-client.html
START BACKUP supports the creation of encrypted backups using ENCRYPT PASSWORD=password. Note NDB Cluster never saves the user-furnished password or generated encryption key. In this case, the management client prompts the user for a password.