New in Web Agent 2023.x
Web Agent 2023.11.x
Web Agent 2023.11.3
Web Agent 2023.11.3 is a maintenance release that introduces security enhancements and fixes.
Web Agent 2023.11.2
Web Agent 2023.11.2 is a maintenance release that introduces security enhancements and fixes.
Request handling
We’ve made changes to the Web Agent to improve the security of handling requests from upstream Java servers.
The agent now rejects unsafe uses of path parameters with an HTTP 400
in the following scenarios:
-
The request contains one or more
%2F
or%2f
(encoded forward slash) characters in the path parameters. -
The request contains one or more
%5C
or%5c
(encoded backslash) characters in the path parameters on a Windows server. -
The request includes empty path segments or dot path segments with path parameters. Some example unsafe uses include:
-
/;/
-
/..;
-
/.;
-
/..;parameter/
Legitimate uses of
;
as a path parameter are still permitted. For example, the agent won’t reject this request with thejessionid
parameter:/segment1/segment2/;jsessionid=1234
-
Path parameters (also known as matrix parameters) are used by J2EE and Spring-based Java servers in URL paths. |
Learn more in Path traversal attempts.
TLSv1.3 security protocol
The TLS 1.3 security protocol can now be disabled for OpenSSL if required by adding -TLSv1.3
to the
Security Protocol List.
Web Agent 2023.11
Web Agent 2023.11 is a minor release that introduces new features, functional enhancements, and fixes.
Hardened security of agent responses with JavaScript
All agent responses that contain JavaScript are now protected by a Content-Security-Policy header.
Examples of responses protected by this change include:
-
HTML forms returned by the agent during POST data preservation
-
Preserved browser fragments returned by the agent during authentication
Deployment with Docker
A Dockerfile is now provided to deploy Apache Web Agent to extend and protect an application. For more information, refer to Deploy Web Agent with Docker.
Web Agent 2023.9
Web Agent 2023.9 is a minor release that introduces new features, functional enhancements, and fixes.
Supported platforms
Web Agent 2023.9 supports the following additional platforms:
-
IBM HTTP Server 8.5 for Linux
-
Red Hat JBoss Core Services for Red Hat Enterprise Linux
-
NGINX Plus R30
For more information, refer to Supported operating systems and web servers Web Agent 2023.9.
Web Agent 2023.6
Web Agent 2023.6 is a minor release that introduces new features, functional enhancements, and fixes.
Use Apache Web Agent with Apache directives
Apache Web Agent can now be configured with the following Apache directives, globally or independently for different server locations:
-
AmAgent
to switch the agent on or off -
AmAuthProvider
to use Apache as the policy enforcement point
For more information, refer to Configure Apache Web Agent.
Authentication of Web Agent to PingOne Advanced Identity Cloud and AM
Web Agent agents are automatically authenticated to PingOne Advanced Identity Cloud and AM by a non-configurable authentication module. Authentication chains and modules are deprecated and replaced by nodes, trees, and journeys.
You can now authenticate Web Agent to PingOne Advanced Identity Cloud and AM 7.3 with a journey. The procedure is currently optional, but will be required when authentication chains and modules are removed in a future release.
For more information, refer to Authenticate agents to PingOne Advanced Identity Cloud and Authenticate agents to AM.
Management of agent credentials
An encryption key in agent.conf
is used to decrypt credentials for the agent
profile, the SSL certificate, and the HTTP proxy. By default, the agent caches
the encryption key. A new property Disable Caching of Agent Profile Password Encryption Key
is available to disable caching and require the agent to securely wipe the
encryption key after it is read.
Use the agentadmin --V
command to verify that the agent can decrypt the credentials
correctly.
Web Agent 2023.3
Web Agent 2023.3 is a major release that introduces new features, functional enhancements, and fixes.
Remove HTTP Server header in IIS
In IIS, the agent can now remove the Server
header from all responses.
To enable the feature, set the Remove IIS HTTP Server Header
property to true
.