Uploaded image for project: 'Single Sign On'
  1. Single Sign On
  2. MGNLSSO-291

Subclassing Pac4jConfigProvider from SSO module breaks Magnolia startup of fresh start when no repositories exist yet

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Neutral
    • 3.1.5
    • 3.1.4
    • sso-connector
    • None

    Description

      Steps to reproduce

      1.  Extends Pac4jConfigProvider by a very simple one like this ExtraPac4jConfigProvider.java in a custom Java module such as extended-sites.xml
      2.  Start up a fresh version of Magnolia with the module in the bundle

      .. Logs, screenshots, gifs...

      Expected results

      • System works by design

      .. Justify non-trivial expectations with a link to a doc or a relevant discussion.

      Actual results

      Workaround

      • Let it finish the start up task, then stop and start again the instance

      Development notes

      • Pac4jConfigProvider constructor start its configuration monitoring on "resources" workspace before the workspace being created. Moving these initiation stuffs to the point after the workspace created would help. This should be in the SSO module's start up function info.magnolia.sso.SsoModule.start(ModuleLifecycleContext)

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                viet.nguyen Viet Nguyen
                AdminX
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Bug DoR
                    Task DoD