Description

Upgrading to 4.0.0-alpha-1 totally block us from login to change any config. So we need to safely remove the SSO login extension module first when the customer were in older version of the SSO module. Here is how to safely remove it:
Uninstalling
To fully uninstall the module follow this steps:

Your jaas.config file should look like so:

sso-authentication {
  info.magnolia.sso.jaas.SsoAuthenticationModule requisite;
  info.magnolia.jaas.sp.jcr.JCRAuthorizationModule required;
};
 

Configuration should be reverted to this:
Since it is a change in the configuration of the login, you will need to use a groovy script or do it in rescue mode.

/server/filters/securityCallback/clientCallbacks/magnolia-sso/class = info.magnolia.sso.UserInitiatedRedirectClientCallback
/server/filters/login/class = info.magnolia.sso.SsoLoginFilter
  

Remove the following dependency from your project:

<dependency>
  <groupId>{group-id}</groupId>
  <artifactId>{artifact-id}</artifactId>
  <version>{modules-version}</version>
</dependency>
  

• We need to change the filter chain in one JCR session otherwise it blocks us from changing, or we need to change /server/filters/securityCallback/clientCallbacks/magnolia-sso/class = info.magnolia.sso.UserInitiatedRedirectClientCallback first, then change /server/filters/login/class = info.magnolia.sso.SsoLoginFilter later, or a Groovy script so that it could run in one session

• Please note that the above jaas.config file is for removing the SSO Login Extension module, then you may need our previous jaas.config file which includes 2 login chains for SSO module 4.0.0-alpha-1 version.

.. Logs, screenshots, gifs...

Expected results

• New fixed version should help to address this issue and provide a smooth transition from older version to the new one without any blocking or conflict.

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

Actual results

• As above

Workaround

• Uninstall the extension module first then install the new version which takes some additional steps for deployment. This affect customer uptime when upgrading on their environment.

Development notes

• New fixed version should help to address this issue by implementing the version handler to detect if the extension module was there and fix its JCR configuration
• Please fix to support Magnolia 6.2.x version