[MXS-960] MaxScale Binlog Server does not allow comma to be in password Created: 2016-10-27  Updated: 2016-12-01  Resolved: 2016-10-31

Status: Closed
Project: MariaDB MaxScale
Component/s: binlogrouter
Affects Version/s: None
Fix Version/s: 1.4.4, 2.0.2, 2.1.0

Type: Bug Priority: Minor
Reporter: Chris Calender (Inactive) Assignee: Massimiliano Pinto (Inactive)
Resolution: Fixed Votes: 2
Labels: None


 Description   

If using MaxScale in Binlog Server mode, and you try to issue a CHANGE MASTER .. MASTER_PASSWORD=.. command with a password that happens to have a comma (",") in the password (which is allowed, in general, by MariaDB), then you receive an error:

mysql> CHANGE MASTER TO MASTER_USER='maxscale_repl_user', MASTER_PASSWORD='a,a';
ERROR 1234 (42000): option 'a'' is not supported

If you update the password to contain, say an underscore, instead of a comma, then it works as expected:

mysql> CHANGE MASTER TO MASTER_USER='maxscale_repl_user', MASTER_PASSWORD='a_a';
Query OK, 0 rows affected (0.00 sec)

MaxScale version 1.4.3.

It seems it is parsing on the comma, and ignoring the single quotes surrounding the password.


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