[MXS-1463] Would like Galera Monitor to support TLS Created: 2017-10-05 Updated: 2017-12-01 Resolved: 2017-10-05 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | galeramon |
| Affects Version/s: | 2.1.9 |
| Fix Version/s: | N/A |
| Type: | New Feature | Priority: | Major |
| Reporter: | Pak Chan | Assignee: | Unassigned |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
Hi, I'm setting up MaxScale and Galera cluster, where all access to the databases in the Galera cluster should be encrypted. It turns out that this isn't possible for MaxScale as there doesn't appear to be any support for TLS in GaleraMon; despite MXS-598 implying that there is. This could prevent us from using this solution, especially as the database user used by galeramon can read database metadata. By default, if the galeramon user (see the configuration below) is required to use SSL, the connection fails, and the tcpdump packet captures show that it is attempting to connect without encryption. In an attempt to correct this, I added the ssl parameters to the Galera Monitor section of the MaxScale config file:
This resulted in MaxScale aborting on startup, with the log showing:
|
| Comments |
| Comment by markus makela [ 2017-10-05 ] |
|
The SSL parameters must be defined for the servers that the monitor monitors, not the monitor itself. |
| Comment by Pak Chan [ 2017-10-05 ] |
|
Ah, in that case, that's my misunderstanding. I have an outstanding bug report on the issue with server TLS (MX-1462). Feel free to close this issue. |