Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-5634

SecuritySupport will always be null when accessed prior to being initialized

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.2.2
    • Component/s: None
    • Labels:
      None
    • Magnolia Release:
      5.2.2

      Description

      With MAGNOLIA-5625 we try to retrieve the current User from MgnlContext earlier as we did before. Unfortunately SecuritySupport has not been instantiated at that time so it is null by then. We could cope with that situation (e.g. return null as User and not set createdBy) if later - once the SecuritySupport has been instantiated - we'd get the proper instance from our component provider. But as SecuritySupport is a Singleton we'll always get null now.

      Best would be to define a default implementation for SecuritySupport that's just to be used in the initialization phase and will then be replaced by the configured one, once the later is available. We anyway know that for the initialization phase there's only one super -> the superuser.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              dlipp Daniel Lipp
              Reporter:
              dlipp Daniel Lipp
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response: