Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.5.5, 10.5.6
-
ANY
Description
I completely understand the point that SUPER privilege has been divided in to multiple parts for better privilege management.
Here, we can use "binlog monitor" privilege to view the contents of binary logs. However, when it comes to relay log it require "replication slave admin" privilege. In earlier version, it need "replication slave" privilege to view the contents of relay logs.
https://mariadb.com/kb/en/grant/#replication-slave-admin
It would be nice to consider the same behavior and provide users with "replication slave" privilege to view the relay log contents using "SHOW RELAYLOGS EVENTS" command accordingly
MariaDB [(none)]> select version();
|
+---------------------+
|
| version() |
|
+---------------------+
|
| 10.4.13-MariaDB-log | |
+---------------------+
|
1 row in set (0.00 sec) |
|
|
MariaDB [(none)]>
|
MariaDB [(none)]> show relaylog events in 'relaylog.000030'; |
ERROR 1227 (42000): Access denied; you need (at least one of) the REPLICATION SLAVE privilege(s) for this operation |
MariaDB [(none)]>
|
|
|
MariaDB [(none)]> select version();
|
+----------------+
|
| version() |
|
+----------------+
|
| 10.5.5-MariaDB | |
+----------------+
|
1 row in set (0.00 sec) |
|
|
MariaDB [(none)]> show relaylog events in 'relaylog.000603'; |
ERROR 1227 (42000): Access denied; you need (at least one of) the REPLICATION SLAVE ADMIN privilege(s) for this operation |
MariaDB [(none)]>
|
|
Attachments
Issue Links
- relates to
-
-
- Closed
-
-
-
- Closed
-