[MXS-1277] Improve messages for failed login attempt Created: 2017-05-30  Updated: 2017-12-01  Resolved: 2017-06-06

Status: Closed
Project: MariaDB MaxScale
Component/s: maxadmin
Affects Version/s: 2.1.3
Fix Version/s: 2.0.6, 2.1.4

Type: New Feature Priority: Major
Reporter: Claudio Nanni Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None


 Description   

Upgrading from 1.4.3 to 2.1.3 it's possible you can no longer log in to maxadmin:

$ maxadmin
Unable to connect to MaxScale at localhost, 6603: Connection refused

(MaxScale is listening on 6603)

Trying to connect via the socket:

$ maxadmin -S /tmp/maxadmin.sock
Could connect to MaxScale, but was not authorized.

Although reading the documentation explains everything and how to solve it, it would be good to have more helpful messages explaining why the login failed.

 Comments   
Comment by markus makela [ 2017-06-06 ]

Attempts to use the network interface when a local socket exists now produce the following error:

Found default MaxAdmin socket in: /tmp/maxadmin.sock
 
Try connecting with:	maxadmin -S /tmp/maxadmin.sock

If a user was not authorized to use the socket, maxadmin shows the command which allows the current user to be added to the list of authorized users.

Could connect to MaxScale, but was not authorized.
 
Check that the current user is added to the list of allowed users.
 
 
 
To add this user to the list, execute:
 
 
 
	sudo maxadmin enable account <user>
 
 
 
This assumes that the root user account is enabled in MaxScale.

Generated at Thu Feb 08 04:05:32 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.