[MXS-3366] COM_CHANGE_USER rejected by MaxScale Created: 2021-01-05 Updated: 2021-01-25 Resolved: 2021-01-25 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Authenticator |
| Affects Version/s: | 2.5.6 |
| Fix Version/s: | 2.5.8 |
| Type: | Bug | Priority: | Major |
| Reporter: | markus makela | Assignee: | Esa Korhonen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Sprint: | MXS-SPRINT-123 |
| Description |
|
If the client doesn't send the CLIENT_CONNECT_WITH_DB flag in the initial connection but later on does a COM_CHANGE_USER with a default database, MaxScale will reject the COM_CHANGE_USER and close the session. It seems that the MariaDB documentation for COM_CHANGE_USER mistakenly stated that the database field is optional when in fact it is always sent in the COM_CHANGE_USER. The solution is to always parse the database field. |