[MXS-671] Error Escape Wildcard in Schema name at login Created: 2016-04-15  Updated: 2016-04-15  Resolved: 2016-04-15

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 1.4.1
Fix Version/s: 1.4.2

Type: Bug Priority: Major
Reporter: Bernd Buffen Assignee: markus makela
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

Linux xxxxxx 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) x86_64 GNU/Linux


 Description   

We have a Galera Cluster 3 Nodes and 2 MaxScale server.
One with the old Version 1.1.0, thats working good. And
one new one with Version 1.4.1 which we want to transfer
the Connections to.

Parameter:
Username: A01U_demo
Schema: A01_demo

Maxscale 1.4.1

# mysql -hmdb-ms -uA01U_demo -pxxxx A01_demo   <-- dosent work
 
but
 
# mysql -hmdb-ms -uA01U_demo -pxxxx            <-- works
 
and this
 
# mysql -hmdb-ms -uA01U_demo -pxxxx            <-- works
 
> use A01_demo;                              <-- also works
 
 
 
CONFIG
 
 
 
[maxscale]
 
threads=4
 
auth_all_servers=true
 
strip_db_esc=true

...
...

log:

2016-04-14 14:30:08   notice : RR: login attempt for user 'A01U_demo', authentication failed.
 
and in Version 1.1.0 both working!!



 Comments   
Comment by markus makela [ 2016-04-15 ]

The strip_db_esc is a service parameter: https://mariadb.com/kb/en/mariadb-enterprise/mariadb-maxscale/maxscale-configuration-usage-scenarios/#service

Can you try moving the strip_db_esc=true under the right service definition, not in the global maxscale section?

Comment by Bernd Buffen [ 2016-04-15 ]

oh oh, thanks a lot. i have move the parameter and every things works fine now

Comment by markus makela [ 2016-04-15 ]

That's great to hear. I'll close this as Not A Bug.

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