Using the same user on UI and API calls resets the configs

[mwandres-hashgraph]

Problem description

When you are logged on the UI and set filters for a given GET request, these filters will overwrite the filter set by API setters - leading to confusing behavior of the GET requests.

Step to reproduce

1. Open the UI and log on with a given user (lets call it A)
2. Log on to the Guardian with the same user A via console
3. Set the filters for the user on the UI to something different than you will request via the API and apply the filters. Leave the UI open.
4. (Maybe you need to log on again via console as your UI usage rendered the JWT of the user obsolete) Set the filters to something different then you used in step 3 and execute the GET call with them
5. The result will not be what you expect according to the filters you handed over to the GET request.
6. Close the browser with the Guardian UI
7. Repeat step 4. The GET response should now be as expected.

Expected behavior

The actions on the UI should not have any implications on the setters handed over via any API calls.