Files
MaxScale/Documentation/Authenticators/MySQL-Authenticator.md
Markus Makela d938f0e72f Add custom cache directory for MySQLAuth
The MySQLAuth authenticator can now store the cached credentials in a
custom location. This is intended for the binlogrouter, which currently
uses a different location for the user cache.

The MySQL authentication modules now have their own document in the
Authenticators directory. Right now this document only describes the
general details of the MySQL authentication and the new option.
2016-10-20 09:26:54 +03:00

1.0 KiB

MySQL Authenticator

The MySQLAuth and MySQLBackendAuth modules implement the client and backend authentication for the MySQL native password authentication. This is the default authentication plugin used by both MariaDB and MySQL.

These modules are the default authenticators for all MySQL connections and needs no further configuration to work.

Authenticator options

The client authentication module, MySQLAuth, supports authenticator options.

cache_dir

The location where the user credential cache is stored. The default value for this is <cache dir>/<service name>/<listener name>/cache/ where <cache dir> by default is /var/cache.

Each listener has its own user cache where the user credential information queried from the backends is stored. This information is used to authenticate users if a connection to the backend servers can't be made.

Example configuration

[Read-Write Listener]
type=listener
service=Read-Write Service
protocol=MySQLClient
port=4006
authenticator=MySQLAuth
authenticator_options=cache_dir=/tmp