Known issues
Known issues in Web Agent 2023.9
| Issue | Comment |
|---|---|
AMAGENTS-6046: convert_request_after_authn_post writes to /tmp instead of configured PDP directory |
Unresolved |
AMAGENTS-5985: Interactive installation using existing agent configuration files duplicate properties which are commented out |
Unresolved |
AMAGENTS-5958: Invalid error AMConfigurationException generated in the log |
Unresolved |
AMAGENTS-5777: IIS web agent zip file includes 32bit DLL |
Unresolved |
AMAGENTS-5718: Custom Login mode 2 doesn’t correctly process composite advice. |
Unresolved |
AMAGENTS-5594: Web agent will return 403 errors if OpenSSL libraries aren’t loaded. |
Unresolved |
AMAGENTS-5032: WPA: 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 does not handle specific case for Not-Enforced URL and one level wildcard properly |
Unresolved |
AMAGENTS-4590: login-fragment-relay page should have charset specified. |
Unresolved |
AMAGENTS-4486: When using cookie.secure with http we should fail early. |
Unresolved |
AMAGENTS-3992: WPA: com.forgerock.agents.config.hostmap does not seem to use the IP address |
Unresolved |
AMAGENTS-3663: Nginx Agent print absolute build path into debug logs |
Unresolved |
AMAGENTS-3506: If there are permissions issues with password file with installation on IIS then the log messages are not helpful |
Unresolved |
AMAGENTS-2813: Agents Logout perform logout multiple times |
Unresolved |
AMAGENTS-2755: Currently when setting up the agent it is necessary to have a client certificate file when using S Channel |
Unresolved |
Known issues in Web Agent 2023.6
| Issue | Comment |
|---|---|
AMAGENTS-6046: convert_request_after_authn_post writes to /tmp instead of configured PDP directory |
Unresolved |
AMAGENTS-5995: Don’t extend user session for not enforced url with fetch attributes enabled |
Fixed in 2023.9 |
AMAGENTS-5985: Interactive installation using existing agent configuration files duplicate properties which are commented out |
Unresolved |
AMAGENTS-5833: WPA 403 error on /agent/cdsso-oauth2 with invalid jwt.aud.whitelist parameter value |
Fixed in 2023.9 |
AMAGENTS-5777: IIS web agent zip file includes 32bit DLL |
Unresolved |
AMAGENTS-5718: Custom Login mode 2 doesn’t correctly process composite advice. |
Unresolved |
AMAGENTS-5594: Web agent will return 403 errors if OpenSSL libraries aren’t loaded. |
Unresolved |
AMAGENTS-5495: Web agent validator reports access to OpenSSL v.1.1.x instead of v3.x |
Fixed in 2023.9 |
AMAGENTS-5032: WPA: 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 does not handle specific case for Not-Enforced URL and one level wildcard properly |
Unresolved |
AMAGENTS-4590: login-fragment-relay page should have charset specified. |
Unresolved |
AMAGENTS-4486: When using cookie.secure with http we should fail early. |
Unresolved |
AMAGENTS-3992: WPA: com.forgerock.agents.config.hostmap does not seem to use the IP address |
Unresolved |
AMAGENTS-3663: Nginx Agent print absolute build path into debug logs |
Unresolved |
AMAGENTS-3506: If there are permissions issues with password file with installation on IIS then the log messages are not helpful |
Unresolved |
AMAGENTS-2813: Agents Logout perform logout multiple times |
Unresolved |
AMAGENTS-2755: Currently when setting up the agent it is necessary to have a client certificate file when using S Channel |
Unresolved |
AMAGENTS-2724: WPA: Custom login does not work, if agent is installed in different location than root |
Duplicates AMAGENTS-5981 |
Known issues in Web Agent 2023.3
| Issue | Comment |
|---|---|
AMAGENTS-6046: convert_request_after_authn_post writes to /tmp instead of configured PDP directory |
Unresolved |
AMAGENTS-5995: Dont extend user session for not enforced url with fetch attributes enabled |
Fixed in 2023.9 |
AMAGENTS-5985: Interactive installation using existing agent configuration files duplicate properties which are commented out |
Unresolved |
AMAGENTS-5833: WPA 403 error on /agent/cdsso-oauth2 with invalid jwt.aud.whitelist parameter value |
Fixed in 2023.9 |
AMAGENTS-5777: IIS web agent zip file includes 32bit DLL |
Unresolved |
AMAGENTS-5495: Web agent validator reports access to OpenSSL v.1.1.x instead of v3.x |
Fixed in 2023.9 |
AMAGENTS-5594: Web agent will return 403 errors if OpenSSL libraries aren’t loaded. |
Unresolved |
AMAGENTS-5032: WPA: 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 does not handle specific case for Not-Enforced URL and one level wildcard properly |
Unresolved |
Known issues in Web Agent 5.10.x
| Issue | Comment |
|---|---|
AMAGENTS-5833: WPA 403 error on /agent/cdsso-oauth2 with invalid jwt.aud.whitelist parameter value |
Fixed in 2023.9 |
AMAGENTS-5777: IIS web agent zip file includes 32bit DLL |
Unresolved |
AMAGENTS-5495: Web agent validator reports access to OpenSSL v.1.1.x instead of v3.x |
Fixed in 2023.9 |
AMAGENTS-5594: Web agent will return 403 errors if OpenSSL libraries aren’t loaded. |
Unresolved |
AMAGENTS-5032: WPA: Native agents for windows do not correctly use unicode for the file system, resulting in configured files with garbled names. |
Unresolved |
AMAGENTS-4984: Setting samesite cookie to lax will cause the agent auth flow to fail if we are using different sites |
Duplicates AMAGENTS-5189 |
AMAGENTS-4672: Web Agent does not handle specific case for Not-Enforced URL and one level wildcard properly |
Unresolved |
Known issues in Web Agent 5.9.x
| Issue | Comment |
|---|---|
AMAGENTS-5068: performance issue in AMAGENTS-4716 fix |
Fixed in 5.10.0 |
AMAGENTS-4795: POST Data Sticky Load Balancing Cookie Name configuration option isn’t working |
Fixed in 5.10.0 |
AMAGENTS-4897: config.fallback.mode doesn’t work for not-enforced url configuration |
Fixed in 5.10.0 |