hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Documentation update regarding support for wildcard hostnames

Browse Source 
Added short descriptions and some warnings to Release-Notes and
Limitations.
This commit is contained in:
Esa Korhonen
2017-01-15 22:17:36 +02:00
parent 936f8c438f
commit c2e14161bd
2 changed files with 20 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
Documentation/About/Limitations.md
View File

@ -251,9 +251,19 @@ need to be truncated to valid block lengths before starting the avrorouter.
## MySQL Authentication Related Limitations (MySQLAuth)
* MariaDB MaxScale can not manage authentication that uses wildcard matching in hostnames
in the mysql.user table of the backend database. The only wildcards that can be
used are in IP address entries.
* MariaDB MaxScale supports authentication that uses wildcard matching in
hostnames in the mysql.user-table of the backend database. For IP-address
entries either '%' or '_'-wildcards are accepted, they should not be mixed
in the same entry. For text addresses both wildcards can be mixed.
* When wildcards are used with text-form hostnames, MariaDB MaxScale uses
the `getnameinfo()`-function (from glibc) to perform the reverse DNS lookup.
This is a slow operation, which will stall the calling thread for an
unspecified time. The lookup is only performed if the mysql.user-table
contains a text hostname with wilcards for the client. Also, do note that
the IP and hostname seen by the backend will be those of the machine running
MariaDB MaxScale, while the username and password will be those of the
original client.
* MySQL old style passwords are not supported. MySQL versions 4.1 and newer use
a new authentication protocol which does not support pre-4.1 style passwords.