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.

        This is the controller panel for Smart Panels app

            [OPT-1924] Extract user authorizations out of the session storage

            There are no comments yet on this issue.

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

                Created:
                Updated:
                Resolved: