Manage the PingAccess agent for Windows configuration through the paa.conf and agent.properties configuration files.
The C:/Apache24/conf/paa.conf file contains the following configuration options:
Parameter | Definition | Default Value |
---|---|---|
PaaCertificateDir |
String value containing the path to the certificates extracted from the .properties files. |
|
PaaEnabled |
Determines whether the agent is enabled or disabled for a
specific server configuration. Valid values are
This value can be set globally; set for individual virtual hosts, directories, locations, or files; or both. The agent follows the most specific value that you set. Note:
If you disable the PaaEnabled parameter
globally, ensure that the PaaEnabled
directive is set to For example, adding this text to an included configuration file enables PingAccess for the /pa/var/www/html/one directory.
Adding this text to an included configuration file disables
PingAccess for all
content in the /var/www/html/two directory
except for files named
|
|
PaaPropertyFiles |
List of .properties files that store configuration data used to connect the agent to the PingAccess engine nodes that the agent will communicate with. |
conf.d/agent.properties |
PaaEnabledNoteName |
An optional parameter that defines a note name. If a request
includes a note with this name and a value of
To use this feature, you must deploy a custom module to include this note with the correct value. |
|
Agent.properties
The configured agent.properties files can contain the following properties:
Property | Definition | Default Value |
---|---|---|
|
The URI scheme used to connect to the engine node. Acceptable values are:
|
|
|
The PingAccess host name. |
The value in the agent node's |
|
The port that the agent connects to on the PingAccess host. Tip:
This value is defined in the PingAccess run.properties file. |
Defined in the PingAccess admin console |
|
The unique agent name that identifies the agent in PingAccess. |
Defined in the PingAccess admin console |
|
The password which is used to authenticate the agent to the engine. |
Defined in the PingAccess admin console |
|
The base64-encoded public certificate which is used to establish HTTPS trust by the agent to the PingAccess engine. Note:
If you are having difficulty connecting an agent to the PingAccess engine, complete the following steps to verify that the Agent Trusted Certificate is configured correctly:
|
Generated by PingAccess |
|
The number of connections that a single web server worker process
maintains to the PingAccess
engine defined in the
|
|
|
The maximum amount of time, in milliseconds, that an agent request made to PingAccess can take. If this time is exceeded, the client receives a generic 500 Server Error response. |
|
|
The maximum amount of time, in milliseconds, that the agent can take to connect to the PingAccess engine. If this time is exceeded, the client receives a generic 500 Server Error response. |
|
|
The maximum amount of time, in milliseconds, that a web server worker process waits for a response to a policy cache request sent to other web server worker processes. |
|
|
The network port that web server processes use to publish policy cache requests to other web server worker processes. This port is bound to the localhost network only. |
|
|
The network port that web server processes use to receive policy cache requests from other web server worker processes. This port is bound to the localhost network only. |
3032 |
|
The maximum number of tokens that are stored in the policy cache
for a single web server worker process. A value of
|
0 |
|
Determines whether policy decision caching is enabled or
disabled. A value of You might want to use this option for custom rules created using the PingAccess SDK that involve data that changes with every request within a resource and session. Warning:
Disabling caching has a significant impact on the scalability of the PingAccess policy servers, as every rule evaluation is processed by the policy server. Because of the performance penalty, only use this option if necessary. |
0 |
|
The hostname and port of the PingAccess server where the agent should send requests in the event of a failover from the PingAccess host. |
Defined in the PingAccess admin console |
|
The number of seconds to wait before the agent should retry connecting to a failed PingAccess server. |
|
|
The number of times to retry a connection to a PingAccess server after an
unsuccessful attempt. If all retries fail, the agent marks the
PingAccess server as
failed for the duration of the
|
|
|
Controls the type of policy cache used by the agent. There are three valid values for this property:
|
|
|
Determines whether the This header contains the following fields:
Learn more in Agent inventory logging. |
|
|
Specifies additional values to include in the
This property uses the following syntax:
Note:
The specified header fields are case-sensitive. |
This property isn't present by default. |
|
If present, specifies a header that overrides the default
|
This property isn't present by default. |
|
Specifies which token-type to favor when making an access decision if both a cookie and an authorization header token are included in a request. Acceptable values are C for cookie or A for authorization bearer token. Learn more in the token-type, path, and vnd-pi-token-cache-oauth-ttl entries in PAAP agent response in the PingAccess 8.1 documentation. Note:
This property isn't listed in the
agent.properties file by default.
To configure |
|
|
If present, specifies a value or values that prompts PingAccess to block a request if it finds one or more of them in the request body. When defining these values, you can:
The following example demonstrates how to block some common XSS characters:
Note:
Blocked requests are recorded as error entries in the PingAccess log. To get more details about why a particular request was blocked, set the log level to debug and review these error entries. |
This property isn't present by default. |
|
If present, specifies a value or values that prompts PingAccess to block a request if it finds one or more of them in the request URI. When defining these values, follow the syntax established in the
The following example demonstrates how to block some common URI characters:
|
This property isn't present by default. |
|
If present, specifies a value or values that prompts PingAccess to block a request if it finds one or more of them in the request's query parameters. When defining these values, follow the syntax established in the
The following example demonstrates how to block some common query characters:
|
This property isn't present by default. |
|
If present, specifies a value or values that prompts PingAccess to block a request if it finds one or more of them in the request's form parameters. Important:
The request must have a When defining these values, follow the syntax established in the
The following example demonstrates how to block some common form characters:
|
This property isn't present by default. |
|
Set a custom status code to display when the agent blocks a request because of a bad XSS character. Tip:
When configuring HTTP status codes initially, consider using a 500 error code to create more obvious test results. After you complete testing, set the HTTP status code to a more reasonable value, such as a 400 error code. The following example demonstrates how to set an XSS HTTP status code:
|
This property isn't present by default. |
|
Set a custom status code to display when the agent blocks a request because of a bad URI character. The following example demonstrates how to set a URI HTTP status code:
|
This property isn't present by default. |
|
Set a custom status code to display when the agent blocks a request because of a bad query character. The following example demonstrates how to set a query HTTP status code:
|
This property isn't present by default. |
|
Set a custom status code to display when the agent blocks a request because of a bad form character. The following example demonstrates how to set a form HTTP status code:
|
This property isn't present by default. |
Add comments to the agent.properties files if necessary. The
agent ignores lines beginning with the #
or !
characters.
If you make changes to the agent.properties file, you must restart the web server.
Learn more about improving agent performance in the Performance tuning guide.