[MXS-356] Connection timeouts for authentication are not configurable Created: 2015-09-07  Updated: 2018-02-08  Resolved: 2015-09-08

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 1.2.0
Fix Version/s: 1.2.1

Type: Bug Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MXS-306 User authentication fails when using ... Closed
relates to MXS-1657 Use authentication fails on backend s... Closed

 Description   

The timeouts for the network connections that are used to fetch the authentication data are not configurable. This would mean that slow networks do not work at all.



 Comments   
Comment by Johan Wikman [ 2015-09-07 ]

Could you provide some more information about this. Is this something we can fix?

Comment by markus makela [ 2015-09-07 ]

Adding three new parameters under the [maxscale] section should fix it. These parameters would control the read, write and connect timeouts used for authentication.

Comment by Dipti Joshi (Inactive) [ 2015-09-09 ]

markus makela Please provide link too updated documentation explaining the use of this new configuration parameter.

Comment by markus makela [ 2015-09-09 ]

Here's the updated documentation: https://github.com/mariadb-corporation/MaxScale/blob/develop/Documentation/Getting-Started/Configuration-Guide.md#auth_connect_timeout

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