[MXS-4683] ssl parameters specified on the bootstrap server are not copied to the rest Created: 2023-07-26 Updated: 2023-07-26 Resolved: 2023-07-26 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | xpandmon |
| Affects Version/s: | 6.4, 22.08, 23.02 |
| Fix Version/s: | 6.4.8, 22.08.7, 23.02.3 |
| Type: | Bug | Priority: | Major |
| Reporter: | susil.behera | Assignee: | Johan Wikman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Builds> |
||
| Issue Links: |
|
||||||||
| Description |
|
SSL parameters specified on the bootstrap server are not copied down to the volatile ones. This is causing SSL setup between MaxScale and XPAND not working properly. Repro 2. Configure maxscale with one xpand node as a server
[xpand1]
[Read-Only-Service] [Read-Only-Listener] 3. start maxscale 4. show server shows ssl=true only for one xpand node, for the remaining it's ssl=false |
| Comments |
| Comment by Johan Wikman [ 2023-07-26 ] |
|
Now the following parameters are copied from the bootstrap server(s) when the dynamic servers are created when dynamic_node_detection is true: max_routing_connections, persistmaxtime, persistpoolmax, proxy_protocol, ssl, ssl_ca, ssl_cert, ssl_cert_verify_depth, ssl_cipher, ssl_key, ssl_verify_peer_certificate, ssl_verify_peer_host, ssl_version. That is, if ssl parameters have been specified for the bootstrap server(s) then ssl will be used also when connections are created to the dynamic ones. |