Search Results
https://dev.mysql.com/doc/mysql-installer/en/server-accounts-roles.html
MySQL User Accounts (Optional) Click Add User or Edit User to create or modify MySQL user accounts with predefined roles. To create a new MySQL account that uses Windows authentication, enter the user name and then select a value for Host and Role.
https://dev.mysql.com/doc/refman/8.4/en/account-locking.html
MySQL supports locking and unlocking user accounts using the ACCOUNT LOCK and ACCOUNT UNLOCK clauses for the CREATE USER and ALTER USER statements: When used with CREATE USER, these clauses specify the initial locking state for a new account. The ...In the absence of either clause, the account is created in an unlocked ...For upgrades from MySQL versions older than ...
https://dev.mysql.com/doc/refman/8.4/en/server-system-variables.html
For CREATE USER and ALTER USER statements used to manage MySQL account definitions, it determines what authentication factor or factors may be specified, where “factor” corresponds to an authentication method or plugin associated with an account. Because authentication_policy applies only when accounts are created or altered, changes to its value have no effect on existing user ...Note Although the authentication_policy system variable places certain constraints on the authentication-related ...
https://dev.mysql.com/doc/refman/8.4/en/replication-privilege-checks-account.html
It is recommended that you never give any ACL privileges to the PRIVILEGE_CHECKS_USER account, including CREATE USER, CREATE ROLE, DROP ROLE, and GRANT OPTION, and do not permit the account to update the mysql.user table. With these privileges, the ... The user account that is specified using the CHANGE REPLICATION SOURCE TO statement as the PRIVILEGE_CHECKS_USER account for a replication channel must have the REPLICATION_APPLIER privilege, otherwise the replication applier thread does not ...
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/refman/8.4/en/performance-schema-accounts-table.html
The accounts table has these indexes: Primary key on (USER, HOST) . The accounts table contains a row for each account that has connected to the MySQL server. For each account, the table counts the current and total number of connections. To set ...
https://dev.mysql.com/doc/refman/8.4/en/reserved-accounts.html
During data directory initialization, MySQL creates user accounts that should be considered reserved: 'root'@'localhost: Used for administrative purposes. This account has all privileges, is a system account, and can perform any operation. Strictly ... One part of the MySQL installation process is data directory initialization (see Section 2.9.1, “Initializing the Data ...
https://dev.mysql.com/doc/refman/8.4/en/account-management-statements.html
MySQL account information is stored in the tables of the mysql system schema. When the read_only system variable is enabled, account-management statements require the CONNECTION_ADMIN privilege (or the deprecated SUPER privilege), in addition to ...
https://dev.mysql.com/doc/heatwave-aws/en/heatwave-aws-account-management.html
Account Management 21 Account Management This chapter discusses region management, service limits, and billing for MySQL HeatWave on AWS. Manage Regions Service Limits Billing Viewing OCID of the TenancyUse the Oracle Cloud Infrastructure (OCI) ...
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 ...For example: GRANT ALL ON db1.* TO 'jeffrey'@'localhost'; GRANT 'role1', 'role2' TO 'user1'@'localhost', 'user2'@'localhost'; GRANT SELECT ON world.* TO 'role3'; The host name part of the account or role name, if omitted, defaults to ...