[Bug]: UI login to new local on the same domain after configuration change get unauthorized on some of the calls

[nopcoder]

What happened?

While switching between configurations of different lakeFS setups, specifically changes to authorization, I encountered issues with the auth/encrypt/secret_key and setting up a new lakeFS instance on the same domain.

On the second lakeFS setup, login passes sometimes, but:

1. It displays the same login information while keeping the login/password fields disabled until a full refresh.
2. While you can access the "Create Sample Repository" option, the UI hangs while listing objects.

Following screenshot of the second state after login to the new lakeFS asking to create sample repository:

Expected behavior

lakeFS should handle the case where previous session was not part of the same lakeFS setup and enable smooth login experience without failing on requests or hang on login.

lakeFS version

v1.50.0

How lakeFS is installed

No response

Affected clients

No response

Relevant log output

Contact details

No response