From 55c2da1f643651d41d8e4724cd616c260e9da422 Mon Sep 17 00:00:00 2001 From: Markus Makela Date: Tue, 3 Nov 2015 11:03:47 +0200 Subject: [PATCH] Fix to MXS-54: https://mariadb.atlassian.net/browse/MXS-54 Added a new configuration parameter that allows the user to control whether authentication warning messages are logged. --- Getting-Started/Configuration-Guide.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/Getting-Started/Configuration-Guide.md b/Getting-Started/Configuration-Guide.md index 7b145d7cb..b41d51391 100644 --- a/Getting-Started/Configuration-Guide.md +++ b/Getting-Started/Configuration-Guide.md @@ -371,6 +371,12 @@ Enabling this feature will transform wildcard grants to individual database gran The retry_on_failure parameter controls whether MaxScale will try to restart failed services and accepts a boolean value. This functionality is enabled by default to prevent services being permanently disabled if the starting of the service failed due to a network outage. Disabling the restarting of the failed services will cause them to be permanently disabled if the services can't be started when MaxScale is started. +#### `log_auth_warnings` + +Enable or disable the logging of authentication failures and warnings. This parameter takes a boolean value. + +MaxScale normally suppresses warning messages about failed authentication. Enabling this option will log those messages into the message log with details about who tried to connect to MaxScale and from where. + #### `connection_timeout` The connection_timeout parameter is used to disconnect sessions to MaxScale that have been idle for too long. The session timeouts are disabled by default. To enable them, define the timeout in seconds in the service's configuration section.