Incompatible changes
Incompatible changes refer to changes that impact existing functionality and might have an effect on your migration from a previous release. Before you upgrade, review these lists and make the appropriate changes to your scripts and plugins.
Incompatible changes in Java Agent 2023.9
Tomcat Java Agent software update
The agent.jar isn’t required for drop-in software update to
Java Agent 2023.9. If the file is present in the container, delete it as
described in
Tomcat Java Agent software update.
JBoss and WildFly Java Agent software update
You must now provide the full path to
jee-agents-sdk-version.jar
in the module.xml file for drop-in software update to Java Agent 2023.9.
The following libraries are no longer required:
-
agent.jar -
jee-agents-jboss-common-version.jar -
tyrus-standalone-client-version.jar
For more information, refer to JBoss and WildFly Java Agent software update.
Jetty Java Agent software update
The agent.jar file isn’t required for drop-in software update to
Java Agent 2023.9. If the file is present in amlogin.mod, delete it
as described in
Jetty Java Agent software update.
WebLogic Java Agent software update
The following libraries aren’t required for drop-in software update to Java Agent 2023.9:
-
agent.jar -
jee-agents-installtools-version.jar
For more information, refer to WebLogic Java Agent software update.
Incompatible changes in Java Agent 2023.3
JDK 8
Support for JDK 8 has been removed.
JDK 11 with WebLogic 12c Java Agent and WebSphere Java Agent
WebLogic 12c Java Agent and WebSphere Java Agent do not support JDK 11, which is the minimum JDK version supported in this release. Consequently, these platforms are not supported in this release. Use Java Agent 5.10 or an earlier version for these platforms.
Incompatible changes in Java Agent 5.10.x
Logback
Log messages in Java Agent and third-party dependencies are now recorded using the Logback implementation of the Simple Logging Facade for Java (SLF4J) API.
From this release, TRACE is the highest log level. In previous releases,
ON was the highest log level.
From this release, when the log level is ON, TRACE level logs are written to
file. In previous releases, TRACE level logs were written to the standard output.
Incompatible changes in Java Agent 5.9.x
Advice Format for Session Upgrade
During session upgrade when both
Enable SSO Token Acceptance
and
Enable Custom Login Mode
are true, the composite advice has the new format:
?authIndexType=composite_advice&authIndexValue=<Advices Value>.
When either property is false, the composite advice is not changed from the
previous format: ?composite_advice=<Advices Value>
AM 5.x.x EOL
AM 5.x.x has reached Product End of Life and is no longer supported. For more information, refer to ForgeRock Product Support Lifecycle Policy | IG and Agents.