[MXS-666] Maxadmin can't login after upgrade to 1.4 Created: 2016-04-11 Updated: 2016-05-31 Resolved: 2016-05-31 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | maxadmin |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | janet | Assignee: | Timofey Turenko |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Description |
|
I just upgraded maxscale from 1.2 to 1.4 and updated the mysql connectiontion user password by maxkey. But then I found I could't login in maxadmin with my original user/passwd. I even tried the default user with admin/mariadb and still no goodluck. |
| Comments |
| Comment by janet [ 2016-04-11 ] |
|
Our passwd include special character such as "+". |
| Comment by markus makela [ 2016-04-13 ] |
|
This most likely is caused by the upgrade done to the maxadmin password encryption. The old encryption was not secure and it was changed to a more secure version. This causes authentication to fail when upgrading from older versions. The process of upgrading the encrypted passwords could be automated but this will most likely be introduced in a later release or could be done via a service offering. Another way to fix this is to remove the old passwd file (located in /var/lib/maxscale/), recreate the encryption key and add the administrative users again. |
| Comment by Johan Wikman [ 2016-05-31 ] |
|
In 2.0, maxadmin can only connect from the same host, using a domain socket. The authentication is handled using Unix users (with root having initial access). Users/passwords from 1.2 and 1.4 will not be recognized or supported. |