Skip to content

Meta data fetched from wrong (first) configuration when a different one is active #441

Open
@blizzz

Description

Steps to reproduce

  1. Create a second configuration
  2. See "metadata valid" success message
  3. 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

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions