Upgrade from 2.1

Install the new version, through packages or tarball. Here are some tips to adapt your current configuration to this new version.

Installation and requirements

As described in installation and requirements sections, there are somes changes:

LSC 2.2 is bundled only for RHEL-like systems 8 and 9, and debian-like systems 11 and 12
LSC 2.2 packages now require Java 21 for running. However, it is still compatible with java 11 and 17 if you build the code yourself.
the GPG key signing the packages has changed to lsc-project-securoty.gpg. You must import this new key.
Nagions plugins are now in the nagios-plugins-lsc package, you must install it if you need them.

XML namespace

Update all configuration files to use the 2.2 XML namespace:

<lsc xmlns="http://lsc-project.org/XSD/lsc-core-2.2.xsd" revision="0">

Logging configuration

The logback.xml file has been improved.

You are encouraged to adapt your specific logback.xml configurations if you have modified them.

There are two evolutions:

Remove the logback initialization blathering at startup. Add these lines in the <configuration> section:

<!-- Stop logback initialization blathering at startup -->
<statusListener class="ch.qos.logback.core.status.NopStatusListener" />

The layout sections must now be surrounded by an encoder tag. You should add this <encoder> tag. For example:

<!-- Standard output to console -->
<appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender">
        <encoder class="ch.qos.logback.core.encoder.LayoutWrappingEncoder">
                <layout class="org.lsc.utils.output.LdifLayout">
                        <Pattern>%date{MMM dd HH:mm:ss} - %-5level - %message%n</Pattern>
                </layout>
        </encoder>
</appender>

Google Apps Destination service

This service is obsolete and has been removed in 2.2 version.

Audits

Audit configuration has been removed in 2.2.

If you have some configuration sections containing:

<audits>
  <audit>
    ...
  </audit>
</audits>

You must remove them and use logback configuration instead.

Behavior change for multi-valued attribute replacement

Before version 2.2, during an entry update, LSC behavior was to systematically replace all values for attributes in FORCE policy.

This could lead to slow modifications, especially for entries with many values, like groups holding many members. However, sometimes it’s cheaper to only add the missing values plus remove the extra values.

LSC 2.2 takes this problematic into consideration.

If (number of missing values + number of extra values) < number of expected values after modification, then LSC applies 2 operations:

1 add of missing values
1 delete of extra values

else, it performs a full replace with all values.