Page Comparison

...

When upgrading to IdP 2.2 you should make the following changes in your configuration files. None of these changes are strictly required but making these changes is necessary for some new features and to remove some warning messages.

Endorsed Libraries

Xerces, one of the two libraries that you should have endorsed when installing the IdP has a new version out. To do this, refer to the Servlet container preparation documentation referenced in the first step of the IdP installation instructions.

...

So, currently, you will have sections that look like this:

<layout class="ch.qos.logback.classic.PatternLayout">
   <Pattern>SOME_PATTERN_STRING</Pattern>
</layout>

and they need to be changed to look like this:

<encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder">
   <Pattern>SAME_PATTERN_AS_ABOVE</Pattern>
   <charset>UTF-8</charset>
</encoder>

...

The LDAP and Relational Database data connectors can now cache their results for a configurable period of time. To enable this you need to configure the cache manager used by the code by adding the following <bean> at the same level as the other <bean> elements in the internal.xml file.

<bean id="shibboleth.CacheManager" class="org.springframework.cache.ehcache.EhCacheManagerFactoryBean" />

...

The IdP currently does not clean up a small piece of state when it finishes a request. This state is associated with something known as the Mapped Diagnostic Context (MDC) of the logging framework. If you maintain your own web.xml file with which you replace the shipped with version, be sure to add the following after the <Listener>> element <listener> element.

<!--  Add IdP SLF4J MDC cleanup filter to all requests -->
<filter>
   <filter-name>SL4JCleanupFilter</filter-name>
   <filter-class>edu.internet2.middleware.shibboleth.common.log.SLF4JMDCCleanupFilter</filter-class>
</filter>
<filter-mapping>
   <filter-name>SL4JCleanupFilter</filter-name>
   <url-pattern>/*</url-pattern>
</filter-mapping>

...