Java Agents

Fixes

Fixes in are cumulative chronologically, by release date. An issue fixed in a maintenance release, such as Java Agent 2023.11.1, isn’t included in a major release, such as Java Agent 2024.3, if the major release was issued before the minor release.

Fixed in Java Agent 2024.11

  • AMAGENTS-6860: The count for the number of allowed by policy requests also counts the redirection to authentication callback

Fixed in Java Agent 2024.9

  • AMAGENTS-6612: Java Agent in accept SSO token mode with custom login false writes JWT tokens to iPlanetDirectoryPro

Fixed in Java Agent 2024.6

  • AMAGENTS-6588: agentadmin writes a log file every time it is started

  • AMAGENTS-6258: Enforce agent’s Logback configuration isolation

Fixed in Java Agent 2024.3

  • AMAGENTS-6131: Tomcat Agent uninstall fails when done a second time

  • AMAGENTS-6119: Menu for uninstall options has number 11 at start rather than 1

  • AMAGENTS-6118: Install help has error in the output

Fixed in Java Agent 2023.11.2

No issues were fixed in this release.

Fixed in Java Agent 2023.11.1

  • AMAGENTS-6258: Enforce agent’s Logback configuration isolation

  • AMAGENTS-6131: Tomcat Agent uninstall fails when done a second time

Fixed in Java Agent 2023.11

No issues were fixed in this release.

Fixed in Java Agent 2023.9

  • AMAGENTS-5999: Cannot initialize logback when invoking classes in the agent SDK

  • AMAGENTS-5928: Remove META-INF/services/javax.servlet.ServletContainerInitializer from the distribution

  • AMAGENTS-5798: Oracle WebLogic admin console fails after patch upgrade

  • AMAGENTS-3798: The AM Conditional Login URL should check that the entry has a | in it

Fixed in Java Agent 2023.6

  • AMAGENTS-5797: java.lang.NullPointerException in org.forgerock.agents.util.UrlParamNormaliser

  • AMAGENTS-5685: JPA: Address bug in cache thawing

  • AMAGENTS-5654: JPA conditional login does not work in case when specific header should match any value

  • AMAGENTS-5600: JPA: Enabling pathinfo and using URL encoding raises exception

  • AMAGENTS-5236: JPA does not respect port/protocol overrides for Not Enforced Rules and Policy Evaluation

Fixed in Java Agent 2023.3

  • AMAGENTS-5550: Changing the log level at runtime stops logging altogether

  • AMAGENTS-5497: Avoid use of the "Agent Tree" for JPA login

  • AMAGENTS-5089: agentadmin --encrypt Agent_Id <password-file> throws error

  • AMAGENTS-4816: Do not invoke rest logout for some special cases

  • AMAGENTS-3912: Avoid displaying a huge stacktrace to the user when the bootstrap properties file cannot be opened

Fixes in Java Agent 5.10.3

  • AMAGENTS-5590: JPA version is not set in config files

Fixes in Java Agent 5.10.2

  • AMAGENTS-5550: Changing the log level at runtime stops logging altogether

  • AMAGENTS-5497: Avoid use of the "Agent Tree" for JPA login

Fixes in Java Agent 5.10.1

  • AMAGENTS-5182: Log level should be WARN if agent-profile authN fails using service=Agent

  • AMAGENTS-5089: agentadmin --encrypt Agent_Id <password-file> throws error

  • AMAGENTS-4816: Agent does not invoke rest logout for special cases

Fixed in Java Agent 5.10

  • AMAGENTS-4677: Reimplement pre-authentication cookie signing

  • AMAGENTS-4667: Bug in i18n not-enforced pattern matching

  • AMAGENTS-4655: Align fragment handling cookie with Web Agent