PingDirectory

Upgrade overview and considerations

Considerations when upgrading to 9.0.0.0 or later

Due to major updates to Spring dependencies, Spring configuration properties in PingData admin console configuration files prior to PingDirectory 9.0.0.0 are not compatible with the most recent admin console bundled with 9.0.0.0 and later versions of PingDirectory products. Attempting to use these older configuration files will result in the console failing to start.

If you are using older PingData admin console configuration files, these should be updated. Replace the following excerpt in the old application.yml file:

spring:
  profiles.active: default
  main.show-banner: false
  thymeleaf.cache: true
  thymeleaf.prefix: classpath:/public/app/

with the following:

spring:
  profiles.active: default
  web.resources:
    # 1 year. Update the corresponding value in MvcConfig if this changes.
    cache.period: 31536000
    add-mappings: false # use our custom mappings instead of the defaults
  main:
    banner-mode: "OFF"
  thymeleaf:
    prefix: classpath:/public/app/

Considerations when upgrading to 8.2.0.0

This upgrade moves to Jetty 9.4. As a result, the HTTPS connection handler will no longer support TLS_RSA ciphers by default. If you use any legacy HTTPS clients that still require TLS_RSA ciphers, modify the ssl-cipher-suite property of the HTTPS Connection Handler to include them.