Comments - MaxScale Configuration & Usage Scenarios
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
MaxScale is currently missing one important feature which prevents it to be a viable option. When clients connect to the DB via MaxScale, you cannot see which users are connected/using to the DB? Only visible user is the MaxScale user(show processlist)? From the monitoring point of view (and auditing) this is not an acceptable approach. When will MaxScale get this functionality?
When clients connect through MaxScale, they will be seen as
user@maxscale-hostname
instead ofuser@client-hostname
. The only thing that will change is the network address where the client appears to be connecting from.You can also see the original usernames and network addresses through the MaxAdmin interface.
Has this been like this always? Since when I tried this on some 1.4x build, It didn't work like this.
MaxScale has never changed the username of the client. The service user given in the configuration file is used for querying user information from the servers so that MaxScale can perform preliminary authentication. The monitors also have their own credentials which could explain why
show processlist
displays open connections created by the monitor user.Here's example output of me connecting to a local server with the
markusjm
user. The server is monitored by MaxScale running on localhost with themaxuser
user. I'm executing aSELECT SLEEP(1000);
from another computer on the same local network and you can see that it gets "converted" tomarkusjm@localhost
.Here's an excerpt from
maxadmin show sessions
showing the real IP of the client.