Known issues
Java Agent 2025.11
| Issue | Comment |
|---|---|
AMAGENTS-6838: JPA will create a JWT cookie in SSO Token Acceptance mode |
Unresolved |
AMAGENTS-6603: JPA: Change all file access to use UTF-8, in JPA itself, and in the installer |
Unresolved |
Java Agent 2025.3
| Issue | Comment |
|---|---|
AMAGENTS-6838: JPA will create a JWT cookie in SSO Token Acceptance mode |
Unresolved |
AMAGENTS-6615: agentadmin option "--getEncryptKey" doesn’t work on Windows |
Fixed in 2025.11 |
AMAGENTS-6603: JPA: Change all file access to use UTF-8, in JPA itself, and in the installer |
Unresolved |
Java Agent 2024.11
| 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 |
Fixed in 2025.3 |
AMAGENTS-6615: agentadmin option "--getEncryptKey" doesn’t work on Windows |
Fixed in 2025.11 |
AMAGENTS-6603: JPA: Change all file access to use UTF-8, in JPA itself, and in the installer |
Unresolved |
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 |
Fixed in 2025.3 |
AMAGENTS-6615: agentadmin option "--getEncryptKey" doesn’t work on Windows |
Fixed in 2025.11 |
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" doesn’t work on Windows |
Fixed in 2025.11 |
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 |