Known issues
Web Agent 2025.11
| Issue | Comment |
|---|---|
AMAGENTS-5718: Custom Login mode 2 doesn’t correctly process composite advice |
Unresolved |
AMAGENTS-5032: Native agents for windows do not correctly use unicode for the file system, resulting in configured files with garbled names |
Unresolved |
Web Agent 2025.9
| Issue | Comment |
|---|---|
AMAGENTS-5718: Custom Login mode 2 doesn’t correctly process composite advice |
Unresolved |
AMAGENTS-5032: Native agents for windows do not correctly use unicode for the file system, resulting in configured files with garbled names |
Unresolved |
AMAGENTS-4672: Web Agent doesn’t handle specific case for Not-Enforced URL and one level wildcard properly |
Fixed in 2025.11 |
Web Agent 2025.6
| Issue | Comment |
|---|---|
AMAGENTS-5718: Custom Login mode 2 doesn’t correctly process composite advice |
Unresolved |
AMAGENTS-5032: Native agents for windows do not correctly use unicode for the file system, resulting in configured files with garbled names |
Unresolved |
AMAGENTS-4672: Web Agent doesn’t handle specific case for Not-Enforced URL and one level wildcard properly |
Fixed in 2025.11 |
Web Agent 2025.3
| Issue | Comment |
|---|---|
AMAGENTS-7219: Local policy evaluation mode not working |
Fixed in 2025.3.1, 2024.11.1 |
AMAGENTS-6363: Shared user profile attributes |
Won’t fix |
AMAGENTS-5718: Custom Login mode 2 doesn’t correctly process composite advice |
Unresolved |
AMAGENTS-5032: Native agents for windows do not correctly use unicode for the file system, resulting in configured files with garbled names |
Unresolved |
AMAGENTS-4672: Web Agent doesn’t handle specific case for Not-Enforced URL and one level wildcard properly |
Fixed in 2025.11 |
Web Agent 2024.11
| Issue | Comment |
|---|---|
AMAGENTS-7219: Local policy evaluation mode not working |
Fixed in 2025.3.1, 2024.11.1 |
AMAGENTS-6905: Apache agent should fail to start if multiple AmAgentID directives are detected |
Fixed in 2025.3 |
AMAGENTS-6904: validate_credential_files issue with config filename that have no path component |
Won’t fix |
AMAGENTS-6749: Agent local configuration files lost formatting |
Fixed in 2025.3 |
AMAGENTS-6363: Shared user profile attributes |
Unresolved |
AMAGENTS-6306: Infinite apache error log caused by pipe error |
Won’t fix |
AMAGENTS-6279: X-frame option is not coming in response header for Application url when fragment redirect is enabled |
Fixed in 2025.3 |
AMAGENTS-5718: Custom Login mode 2 doesn’t correctly process composite advice |
Unresolved |
AMAGENTS-5032: Native agents for windows do not correctly use unicode for the file system, resulting in configured files with garbled names |
Unresolved |
AMAGENTS-4672: Web Agent doesn’t handle specific case for Not-Enforced URL and one level wildcard properly |
Fixed in 2025.11 |
Web Agent 2024.9
| Issue | Comment |
|---|---|
AMAGENTS-6749: Agent local configuration files lost formatting |
Fixed in 2025.3 |
AMAGENTS-6729: Looping after Authentication in session quota mode with -25 / 403 errors |
Fixed in 2024.11 |
AMAGENTS-6363: Shared user profile attributes |
Unresolved |
AMAGENTS-6306: Infinite apache error log caused by pipe error |
Unresolved |
AMAGENTS-6279: X-frame option is not coming in response header for Application url when fragment redirect is enabled |
Fixed in 2025.3 |
AMAGENTS-5958: Invalid error AMConfigurationException generated in the AM log |
Fixed in 2024.11 |
AMAGENTS-5718: Custom Login mode 2 doesn’t correctly process composite advice |
Unresolved |
AMAGENTS-5032: Native agents for windows do not correctly use unicode for the file system, resulting in configured files with garbled names |
Unresolved |
AMAGENTS-4672: Web Agent doesn’t handle specific case for Not-Enforced URL and one level wildcard properly |
Fixed in 2025.11 |
Web Agent 2024.6
| Issue | Comment |
|---|---|
AMAGENTS-6628: Fragment replay is broken with custom login mode 2 |
Fixed in 2024.9, 2023.11.1 |
AMAGENTS-6527: WPA SSL_shutdown shutdown while in init errors in agent log |
Fixed in 2024.9, 2023.11.2 |
AMAGENTS-6363: Shared user profile attributes |
Unresolved |
AMAGENTS-6306: Infinite apache error log caused by pipe error |
Unresolved |
AMAGENTS-6279: X-frame option is not coming in response header for Application url when fragment redirect is enabled |
Fixed in 2025.3 |
AMAGENTS-6215: "Not Enforced Client IP List" abnormal |
Fixed in 2024.9, 2023.11.2 |
AMAGENTS-5958: Invalid error AMConfigurationException generated in the AM log |
Fixed in 2024.11 |
AMAGENTS-5718: Custom Login mode 2 doesn’t correctly process composite advice |
Unresolved |
AMAGENTS-5032: Native agents for windows do not correctly use unicode for the file system, resulting in configured files with garbled names |
Unresolved |
AMAGENTS-4672: Web Agent doesn’t handle specific case for Not-Enforced URL and one level wildcard properly |
Fixed in 2025.11 |
Web Agent 2024.3
| Issue | Comment |
|---|---|
AMAGENTS-6628: Fragment replay is broken with custom login mode 2 |
Fixed in 2024.9, 2023.11.1 |
AMAGENTS-6527: WPA SSL_shutdown shutdown while in init errors in agent log |
Fixed in 2024.9, 2023.11.2 |
AMAGENTS-6494: Agents local policy eval fails. Agent name and policy application name are switched |
Fixed in 2024.6, 2023.11.1 |
AMAGENTS-6363:websites sharing a cache sometimes don’t get the expected headers set because of cache sharing issues in the agent |
Unresolved |
AMAGENTS-6306: infinite apache error log caused by pipe error |
Unresolved |
AMAGENTS-6289: AM_SYSTEM_LOG_FILES only works for debug.log |
Fixed in 2024.6 |
AMAGENTS-5958: Invalid error AMConfigurationException generated in the AM log |
Fixed in 2024.11 |
AMAGENTS-5718: Custom Login mode 2 doesn’t correctly process composite advice. |
Unresolved |
AMAGENTS-5032: Native agents for windows do not correctly use unicode for the file system, resulting in configured files with garbled names. |
Unresolved |
AMAGENTS-4672: Web Agent doesn’t handle specific case for Not-Enforced URL and one level wildcard properly |
Fixed in 2025.11 |
AMAGENTS-3663: Nginx Agent print absolute build path into debug logs |
Fixed in 2024.6 |
AMAGENTS-2813: Agents Logout perform logout multiple times |
Not a defect |
AMAGENTS-2755: Currently when setting up the agent it’s necessary to have a client certificate file when using Schannel |
Won’t fix |