Upgrade considerations
The following modifications since PingFederate 13.0 might affect existing deployments.
- Jersey version upgrade and plugin compatibility
-
We’ve upgraded the internal Jersey library from version 1 to 2. As these versions aren’t compatible, any plugin dependent on Jersey 1, such as the OAuth Playground, will cause PingFederate to fail to operate.
If you have an older version of the OAuth Playground installed, you must either upgrade to OAuthPlayground 5.0, or delete the old OAuthPlayground from your deployment directory before starting PingFederate.
If your
server.logcontains an error similar to the following error, review theserver/default/deploydirectory. You must update or remove any plugin that relies on Jersey 1.x librariesExample errorjava.lang.RuntimeException: java.lang.AbstractMethodError: Receiver class com.sun.jersey.api.uri.UriBuilderImpl does not define orinherit an implementation of the resolved method 'abstract javax.ws.rs.core.UriBuilder uri(java.lang.String)'...
pf.admin.baseurlmust be set-
A defect fix requires the
pf.admin.baseurlproperty to be explicitly set inrun.properties. This prevents admin console URL redirects from failing when PingFederate is accessed through a load balancer with a port that differs frompf.admin.https.port. - Removed support for Java 11
-
Starting with version 13.0, PingFederate no longer supports Java 11. Use Java 17 or Java 21 instead.
Learn more in Java environment.
- Upgrade from PingFederate 8.x
-
Starting with version 13.0, PingFederate no longer supports upgrading from 8.x.