Known issues
Java Agent 2024.9
| Issue | Comment |
|---|---|
AMAGENTS-6838: JPA will create a JWT cookie in SSO Token Acceptance mode |
Unresolved |
AMAGENTS-6809: Monitoring endpoint doesn’t work for Jakarta builds |
Unresolved |
AMAGENTS-6615: agentadmin option "--getEncryptKey" does not work on Windows |
Unresolved |
AMAGENTS-6603: JPA: Change all file access to use UTF-8, in JPA itself, and in the installer |
Unresolved |
Java Agent 2024.6
| Issue | Comment |
|---|---|
AMAGENTS-6615: agentadmin option "--getEncryptKey" does not work on Windows |
Unresolved |
AMAGENTS-6612: Java Agent in accept SSO token mode with custom login false writes JWT tokens to iPlanetDirectoryPro |
Fixed in 2024.9 |
AMAGENTS-6603: JPA: Change all file access to use UTF-8, in JPA itself, and in the installer |
Unresolved |
Java Agent 2024.3
| Issue | Comment |
|---|---|
AMAGENTS-6258: Enforce Agent’s Logback configuration isolation |
Fixed in 2024.6, 2023.11.1 |
AMAGENTS-6078: JPA does not remove the pre-authn cookie in all circumstances |
Won’t fix |
Java Agent 2023.11
| Issue | Comment |
|---|---|
AMAGENTS-6258: Enforce Agent’s Logback configuration isolation |
Fixed in 2024.6, 2023.11.1 |
AMAGENTS-6131: Tomcat Agent uninstall fails when done a second time |
Fixed in 2024.3, 2023.11.1 |
AMAGENTS-6119: Menu for uninstall options has number 11 at start rather than 1 |
Fixed in 2024.3 |
AMAGENTS-6118: Install help has error in the output |
Fixed in 2024.3 |
AMAGENTS-6078: JPA does not remove the pre-authn cookie in all circumstances |
Won’t fix |
Java Agent 2023.9
| Issue | Comment |
|---|---|
AMAGENTS-6131: Tomcat Agent uninstall fails when done a second time |
Fixed in 2024.3, 2023.11.1 |
AMAGENTS-6119: Menu for uninstall options has number 11 at start rather than 1 |
Fixed in 2024.3 |
AMAGENTS-6118: Install help has error in the output |
Fixed in 2024.3 |
AMAGENTS-6078: JPA does not remove the pre-authn cookie in all circumstances |
Won’t fix |
Java Agent 2023.6
| Issue | Comment |
|---|---|
AMAGENTS-5999: Cannot initialize logback when invoking classes in the agent SDK |
Fixed in 2023.9 |
AMAGENTS-5928: Remove META-INF/services/javax.servlet.ServletContainerInitializer from the distribution |
Fixed in 2023.9 |
AMAGENTS-5798: Oracle WebLogic admin console fails after patch upgrade |
Fixed in 2023.9 |
AMAGENTS-4984:Setting samesite cookie to lax will cause the agent auth flow to fail if we are using different sites - |
Duplicates AMAGENTS-5996 |
AMAGENTS-3798: The AM Conditional Login URL should check that the entry has a | in it |
Fixed in 2023.9 |
Java Agent 2023.3
| Issue | Comment |
|---|---|
AMAGENTS-5999: Cannot initialize logback when invoking classes in the agent SDK |
Fixed in 2023.9 |
AMAGENTS-5928: Remove META-INF/services/javax.servlet.ServletContainerInitializer from the distribution |
Fixed in 2023.9 |
AMAGENTS-5798: Oracle WebLogic admin console fails after patch upgrade |
Fixed in 2023.9 |
AMAGENTS-5797: java.lang.NullPointerException in org.forgerock.agents.util.UrlParamNormaliser |
Fixed in 2023.6 |
AMAGENTS-5685: JPA: Address bug in cache thawing |
Fixed in 2023.6 |
AMAGENTS-5654: Conditional login does not work in case when specific header should match any value |
Fixed in 2023.6 |
AMAGENTS-5631: Encrypt-in-place does not overwrite existing password |
Fixed in 2023.6 |
AMAGENTS-5602: Pathinfo stripping is only done for not-enforced rules |
Won’t fix |
AMAGENTS-5601: NotEnforcedRuleHelper instantiates a metrics object, but never uses it. |
Not a defect |
AMAGENTS-5600: Enabling pathinfo and using URL encoding raises exception |
Fixed in 2023.6 |
AMAGENTS-4984: Setting samesite cookie to lax will cause the agent auth flow to fail if we are using different sites |
Duplicates AMAGENTS-5996 |
AMAGENTS-3798: The AM Conditional Login URL should check that the entry has a | in it |
Fixed in 2023.9 |
Java Agent 5.10
| Issue | Comment |
|---|---|
AMAGENTS-5999: Can’t initialize logback when invoking classes in the agent SDK |
Fixed in 2023.9 |
AMAGENTS-5928: Remove META-INF/services/javax.servlet.ServletContainerInitializer from the distribution |
Fixed in 2023.9 |
AMAGENTS-5590: JPA version is not set in config files |
Fixed in 5.10.3 |
AMAGENTS-5798: Oracle WebLogic admin console fails after patch upgrade |
Fixed in 2023.9 |
AMAGENTS-4984: Setting samesite cookie to lax will cause the agent auth flow to fail if we are using different sites |
Duplicates AMAGENTS-5996 |
AMAGENTS-4816: The agent does not invalidate session before redirecting to logout |
Fixed in 2023.3, 5.10.1 |
AMAGENTS-3798: The AM Conditional Login URL should check that the entry has a | in it |
Fixed in 2023.9 |
AMAGENTS-3912: Avoid displaying a huge stacktrace to the user when the bootstrap properties file cannot be opened |
Fixed in 2023.3 |
Java Agent 5.9
| Issue | Comment |
|---|---|
AMAGENTS-4528: Investigate the use of "host" from the session properties |
Fixed in 5.10 |
AMAGENTS-4514: JPA will set 2x set-cookie header for Profile Attributes |
Won’t fix |
AMAGENTS-4181: When the last property in bootstrap properties is a list, the property is ignored |
Won’t fix |
AMAGENTS-4175: One level wildcard does not work when request contains trailing slash for java agents |
Not a defect |
AMAGENTS-3912: Avoid displaying a huge stacktrace to the user when the bootstrap properties file cannot be opened |
Fixed in 2023.3 |