@hmlnarik exactly which tests are failing locally without these fixes? The Account Console doesn't support dynamically changing realms, so I would expect any realm change to be a full page load, setting the basename at that time.

@hmlnarik exactly which tests are failing locally without these fixes? The Account Console doesn't support dynamically changing realms, so I would expect any realm change to be a full page load, setting the basename at that time.

KC server is run on server 8180 but the admin client was targetting only port 8080, assuming that the account UI and REST endpoints are served by the same server. Please see the details in the linked issue

The linked account tests which use both "groups" and "master" realms in a single test failed with
<Router basename="/realms/master/account"> is not able to match the URL "/realms/groups/account/account-security/device-activity" because it does not start with the basename, so the <Router> won't render anything. reported in the browser console.