Authentication failures via socket after primary change

[Vasya Pupkin]

Hello,

I would like to report a bug with MySQL router 8.0.25 and below. Steps to reproduce:

1. Set up MySQL cluster
2. Bootstrap MySQL router with --conf-use-sockets option
3. Configure mysql to use socket, example config:
[client]
socket=/home/mysqlrouter/data/mysql.sock
user=admin
password=SuperSecret
4. Restart current primary server
5. Use mysqlsh setPrimaryInstance() to make restarted server primary after it's back online
5. Run mysql

Expected behavior:
Connection is established as usual

Actual behavior:
ERROR 1045 (28000): Access denied for user 'admin'@'x.x.x.x' (using password: YES)

Additional info:
If connection changed from socket to TCP, connection works. It's even possible to use socket again after successful connection via TCP.