Page created: 12 Sep 2019 |
Page updated: 19 Mar 2020
The PingFederate provisioner-audit.log file records outbound provisioning transactions, intended to facilitate security auditing. The log file is located in the <pf_install>/pingfederate/log directory. Outbound provisioning audit log information may be output to different formats, including database and Splunk.
The following table describes all recorded elements. As needed, elements are configurable by editing the <pf_install>/pingfederate/server/default/conf/log4j2.xml file.
|cycle_id||The unique ID for each provisioning cycle.|
|channel_id||The unique ID of the provisioning channel between source and target.|
|event_type||The type of provisioning events, such as CREATE and UPDATE.|
|source_id||The provisioning Source ID.|
|target_id||The provisioning Target ID.|
|is_success||A flag to show whether the event was successful or not. If the attempt
succeeded, the value is
|non_success_ cause||Description of failure cause.|