The following limitations in this release are inherent to the design, not bugs to be fixed:
Custom Login Redirection Mode Requires AM 6 or Later
Redirect of users to a specific AM instance, an AM site, or website other than AM, requires AM 6 or later versions. For more information, see Login Redirection and Login Conditional Redirection.
Ignore Path Info Properties Is not Supported for NGINX Plus Agent
The NGINX Plus web agent does not support the following ignore path info properties:
IIS Web Agents May Fail to Install When IIS Configuration Is Locked
Installing web agents in IIS may fail with an error similar to the following:
Creating configuration... Error: failed to create module entry for MACHINE/WEBROOT/APPHOST/AgentSite/ (error 0x80070021, line: 1823). The process cannot access the file because another process has locked a portion of the file. (error: 0x21). Installation failed.
This error message means the
agentadmin.exe command cannot
access some IIS configuration files because they are locked.
To work around this issue, perform the following steps:
Open the IIS Manager and select the Configuration Editor.
Unlock the IIS
Retry the web agent installation.
system.webServer/modules module should allow the
installation to finish. However, you may need to unlock other modules depending
on your environment.
Apache HTTP Server Authentication Functionality Not Supported
The web agent replaces authentication functionality provided by Apache, for
mod_auth_* modules. Integration with built-in Apache httpd
authentication directives, such as
is not supported.
IIS Web Agent With Client-Based Sessions Returning HTTP 403 Errors When Accessing Protected Resources
IIS web agents configured for client-based sessions will return HTTP 403 errors
when trying to access a protected resource if
com.sun.identity.client.notification.url is configured.
com.sun.identity.client.notification.url property is removed in this release.
Earlier versions of Web Agent use it to specify the notification listener
for the agent. However, to provide backwards-compatibility
with earlier versions of the agents, AM populates this property when
creating the agent profile.
The value of this property should removed for all agent installations, and must be removed for IIS web agents configured for client-based sessions.
Default Welcome Page Showing After Upgrade Instead of Custom Error Pages
After upgrading, you may see the default Apache welcome pages instead of custom
error pages defined by the Apache
If you encounter this issue, check your Apache
If the custom error pages are not in the document root of the Apache server,
you should enclose the
ErrorDocument directives in
<Directory "/web/docs"> ErrorDocument 403 myCustom403Error.html </Directory>
Refer to the Apache documentation for more details on the
CA Certificate File Name Property not Honored when Client Authentication is not Required in Secure Channel Environments
If you are using the Windows built-in Secure Channel API but your environment does not require client authentication, instead of setting the CA certificate friendly name in the CA Certificate File Name Property, set it in the Public Client Certificate File Name property. For example:
com.forgerock.agents.config.cert.ca.file = com.forgerock.agents.config.cert.file = CA-cert-friendly-name com.sun.identity.agents.config.trust.server.certs = false
Install IIS Web Agents on Child Applications Before Installing in Parent Application
In an IIS environment where you need to protect a parent application and a child application with different web agent configurations, you must install the web agent on the child application before installing the web agent in the parent. Trying to install a web agent on a child that is already protected will result in error.