The PrivacyEx session agent enables the encryption, blocking, and replacement of text in the request and response buffers.
Like the Privacy session agent, this session agent uses a flexible set of rules and configuration options to ensure that sensitive data is treated in an appropriate manner.
Attention: In multi-pipeline environments, do not enable the extended privacy session agent (
PrivacyEx
) for child pipelines that have HBR enabled. If HBR and PrivacyEx
are enabled for a child pipeline, the service can run out of memory and cause the service to restart unexpectedly.The PrivacyEx session agent extends the older Privacy session agent with the following features:
- Faster buffer search: PrivacyEx can search a request or a response once for all terms for which it is trying to filter.
- Internationalization support: PrivacyEx can be used to filter data in a variety of international encoding schemes.
- MD5: If needed, you can apply MD5 hashing to the output of a privacy rule.
Note: Where possible, use PrivacyEx session agent instead of Privacy, which may be deprecated in future releases.
Settings
The following configuration settings are available for the session agent:
- Display Name values are displayed in TMS, which is the recommended method for configuring session agents.
- Name values are displayed in
TealeafCaptureSocket.cfg
.
Display Name | Name | Description |
---|---|---|
Config File |
ConfigFile |
The name of the file containing the rules and actions in use by PrivacyEx session agent. Default value is Privacy.cfg , which is used by the Privacy session agent, too. |
Show Rules in Event Log |
LogRules |
When set to true , PrivacyEx session agent lists the rules and actions in use in the Tealeaf application event log. |
Log Level |
LogLevel |
When enabled and defined, the log level setting defines the logging level of messages inserted into the request in the [privacylog] section.
Note: The
Debug logging level should only be enabled when you are debugging issues with rules and actions. The additional data inserted into the request may cause a significant increase in data volume and decrease in performance. Additionally, unencrypted original data values may be logged at Debug level. When you have finished debugging, remember to reset the logging level. |