Details

    • Type: Sub-task
    • Status: Done
    • Priority: L3 - Default
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2.4.0, 2.4.0-alpha2
    • Component/s: backend
    • Labels:

      Description

      AT:

      • user authorizations are not stored inside the user session but handled by a dedicated service
      • user authorizations are cached by userId in order to avoid calling the engine for each authorization check in Optimize
      • the authorization cache is invalidated/refreshed on session creation/destroy

      Note:
      This prepares the overall removal of session state inside a particular Optimize instance.

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

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

              Dates

              • Created:
                Updated:
                Resolved: