| 1 |
CREATE USER t346; |
| 2 |
GRANT NDB_STORED_USER ON *.* TO t346; |
| 3 |
SELECT password_expired FROM mysql.user WHERE USER = 't346'; |
| 4 |
password_expired |
| 5 |
N |
| 6 |
server 2: |
| 7 |
SELECT password_expired FROM mysql.user WHERE USER = 't346'; |
| 8 |
password_expired |
| 9 |
N |
| 10 |
result_format: 2 |
| 11 |
## When a MySQL server starts up, it has to catch up on all the changes |
| 12 |
## to NDB stored users as recorded in the ndb_sql_metadata table. The snapshots |
| 13 |
## in the table include the output of SHOW CREATE USER. If the local result |
| 14 |
## from SHOW CREATE USER is identical to the one stored in the snapshot, it |
| 15 |
## can mark a user as synchronized without touching their password_last_changed |
| 16 |
## timestamp. |
| 17 |
## |
| 18 |
## We are going to record some output from SHOW CREATE USER in the result file |
| 19 |
## here, so that this test will fail whenever that output changes. Any time |
| 20 |
## that output changes from one release to the next we should respond, either |
| 21 |
## by writing code that expects the change, or by writing a release note to |
| 22 |
## tell users that upgrading will cause password timestamps to get bumped. |
| 23 |
set print_identified_with_as_hex = true; |
| 24 |
SHOW CREATE USER t331@localhost; |
| 25 |
CREATE USER for t331@localhost CREATE USER `t331`@`localhost` IDENTIFIED WITH 'caching_sha2_password' AS 'encrypted_password' REQUIRE NONE PASSWORD EXPIRE DEFAULT ACCOUNT UNLOCK PASSWORD HISTORY DEFAULT PASSWORD REUSE INTERVAL DEFAULT PASSWORD REQUIRE CURRENT DEFAULT |
| 26 |
set print_identified_with_as_hex = false; |
| 27 |
|
| 28 |
## Cleanup |
| 29 |
DROP USER t346; |
| 30 |
DROP USER t331@localhost; |