This guideline list out steps to disable SSO module version 3.1.1. Changes may happen in the future which may affect removing steps.

Step-by-step guide to disable SSO module

  1. Use Groovy app to run remove SSO module Groovy script
    Remove SSO module script
    session = ctx.getJCRSession('config')
    session.getNode('/server/filters/logout').setProperty('class', '') 
    session.getNode('/server/filters/login').setProperty('class', '')
  2. If you configured your "jaas.config" like below, you won't have to restart the instance. Basically we can have multiple login modules configured there:
    JAAS config
    magnolia {
    // ensure user is who he claims he is (check pwd for the user)
     info.magnolia.jaas.sp.jcr.JCRAuthenticationModule requisite;
    // retrieve users ACLs
     info.magnolia.jaas.sp.jcr.JCRAuthorizationModule required;
    sso-authentication {
      info.magnolia.sso.jaas.SsoAuthenticationModule requisite skip_on_previous_success=true;
      info.magnolia.jaas.sp.jcr.JCRAuthorizationModule required;
  3. Last step - optional:

In order to remove SSO module from the bundle, if you just want to completely remove it.

Open project "pom.xml" file and remove SSO module dependency. Rebuild and restart instance.

    <!-- <dependency>
    </dependency> -->


We will not remove '/modules/magnolia-sso' ( or '/modules/sso' in an older version) configuration point, so that in case customer restart the instance without removing the module, it would not be installed again.

Re-enable SSO module

Remove '/modules/magnolia-sso' ( or '/modules/sso' in an older version) configuration point and restart the instance (without removing its dependency in "pom.xml") will trigger module installation. This will bring back SSO module using your previous configured information.