Authentication failed, caused by: illegal base64 data at input byte 4

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: authenticate failed, caused by: illegal base64 data at input byte4

| username: liarby

[TiDB Usage Environment] Testing
[TiDB Version] 8.1.0
[Reproduction Path] Upgrade TiDB 7.1 to 8.1.0 using tiup
[Encountered Issue: Phenomenon and Impact] Unable to log in to the Dashboard

  1. After entering the root password, it prompts [Login failed: authenticate failed, caused by: illegal base64 data at input byte 4]
  2. After changing the password to base64 encoding, the prompt changes to [Login failed: authenticate failed, caused by: crypto/rsa: decryption error]
    [Resource Configuration] Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
    [Attachments: Screenshots/Logs/Monitoring]
    5beb788fa62d461b901cf98de7751b1
    5beb788fa62d461b901cf98de7751b1398×553 10.9 KB

    62256d3b954f4280ce7ff705933afee
    62256d3b954f4280ce7ff705933afee367×552 10.5 KB
2
| username: Kongdom | Original post link

Can the database be logged in normally? Has the PD node corresponding to the dashboard been restarted? Are you using load balancing?

3
| username: ShawnYan | Original post link

@liarby Heard it was resolved? Could it really be a browser issue?

4
| username: liarby | Original post link

Switch to another browser… transfer the dashboard
I switched to Edge and was able to log in, then went back to Chrome and could log in as well.