Meta data fetched from wrong (first) configuration when a different one is active #441
Open
Description
Steps to reproduce
- Create a second configuration
- See "metadata valid" success message
- wonder why auth is not working as expected
Expected behaviour
Meta data of the current config is fetched
Actual behaviour
Config parameter is not send to the server, so meta data of the "1" config is fetched