Cloud Auth Cookie set on global ingress domain causes error when accessing different Optimize instances

XMLWordPrintable

    • Type: Bug Report
    • Resolution: Fixed
    • Priority: L3 - Default
    • 3.6.0-alpha2, 3.6.0
    • Affects Version/s: None
    • Component/s: backend
    • Not defined

      Problem:
      The Authentication cookie is not set according to the sub-path Optimize is served on but on the whole global ingress address, see screenshot

      Steps to reproduce:
      1. Create two clusters on cloud that contain Optimize
      2. Access one of the Optimize instances
      3. Access the other instance

      Actual Result:
      You get error notifications when switching between the instances and have to hard refresh the page.

      Expected result:
      It should just work Auth Cookies should be separate per cluster.

            Assignee:
            Unassigned
            Reporter:
            Sebastian Bathke
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: