Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
2.2.21, 2.3.6
-
None
-
MXS-SPRINT-83, MXS-SPRINT-84, MXS-SPRINT-85
Description
MaxAdmin allows you to see which database users are available for a specific service. For example, by executing the following command:
$ sudo maxadmin show dbusers Splitter-Service
|
User names (Read-Listener): alice@%
|
But MaxAdmin is deprecated now.
MaxCtrl and the REST API are the new way to get information about MaxScale's state. Unfortunately, information about database users doesn't appear to be available at all via MaxCtrl and the REST API.
Database users are not shown by this command:
maxctrl show service Splitter-Service
|
Or this command:
maxctrl list listeners Splitter-Service
|
And this does not even appear to be a valid command:
maxctrl show listener Read-Listener
|
And neither does this:
maxctrl show dbusers Read-Listener
|
And neither does this:
maxctrl show dbusers Splitter-Service
|
I think it is very important to make information about database users available for debugging and troubleshooting purposes, since MaxScale's authentication can get pretty complicated at times.
I think the information about database users should include the following information:
- The user name.
- The host.
- The listener.
- The service.
- The authenticator (e.g. PAMAuth, MySQLAuth, GSSAPIAuth).
- Whether the user has PROXY privileges on any other users. (Definitely relevant for PAMAuth.)
Attachments
Issue Links
- relates to
-
MXS-1716 "show dbusers ...service..." returns empty list when using PAMAuth
- Closed