Cloud user cache scheduler doesn't work because of token

XMLWordPrintable

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

      Brief summary of the bug. What is it ? Where is it ?

      The cloud user cache can't be populated without an access token, so cloud SaaS fails to start

      Steps to reproduce:

      Start Optimize in cloud mode

      Actual result:

      It doesn't start

      Expected result:

      Optimize starts successfully

            Assignee:
            Unassigned
            Reporter:
            Joshua Windels
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: