To log details about your PingAccess agents, you can add custom configuration to the agents and the PingAccess system.
Agent information other than the agent name is not included in agent responses by default. You can customize agents to include the agent header, providing additional information that can be included in logs.
You must edit the /conf/log4j2.xml file to log the information included in the agent header. See Security audit logging for more information.
For more information about agent headers, see https://docs.pingidentity.com/csh?Product=pa-latest&topicname=sjw1565633628332.html .
vnd-pi-agent header allows the agent to
communicate information about itself and its deployment environment to PingAccess.
The value of this header is a map of comma-separated key-value pairs.
- The version of the agent making the request.
- The type of agent and/or the type of platform where the agent resides.
- The hostname of the server where the agent resides.
The syntax for the
vnd-pi-agent value conforms to a dictionary in
this specification, https://httpwg.org/http-extensions/draft-ietf-httpbis-header-structure.html#dictionary, where
member-values are constrained to be an
These header examples are considered semantically equivalent.
vnd-pi-agent: v="1.0.0", h="apache.example.com", t="Apache 2.4.41"
vnd-pi-agent: v="1.0.0", h="apache.example.com" vnd-pi-agent: t="Apache 2.4.41"
vnd-pi-agent: v="1.0.0" vnd-pi-agent: h="apache.example.com" vnd-pi-agent: t="Apache 2.4.41"