20 - Troubleshooting Then Lab
20 - Troubleshooting Then Lab
COM
TROUBLESHOOTING
Ping Identity Education
PINGFEDERATE LOGS
Sample:
2013-08-19 18:20:48,390 DEBUG [AuditLogger] Administrator | UserAdmin,Admin,CryptoAdmin | Login
attempt | Login was successful
Sample:
2013-08-20 16:53:45,635 INFO [com.pingidentity.appserver.jetty.SocketConnector] Not starting
listener class com.pingidentity.appserver.jetty.SocketConnector because port was set to -1
Sample:
2013-08-24 13:34:28,546 | 192.168.238.132:9041 | S | Sent Request | Connection
ID: idp:saml2 (IDP) | AuthnRequest | Target URL:
http://sm6.pinggcslab.sp.com:81/PFIsapiSample/Default.aspx?LOGON_USER=PFuser |
Endpoint: http://sm6.pinggcslab.idp.com:9030/idp/SSO.saml2
§ Rollover:
– The transaction.log, the admin.log, the audit.log and the provisioner.log files roll
over at midnight each day.
› These files can become quite large, back up or remove older files on a routine basis.
– Other PingFederate log files roll over when they reach 10MB.
› The five most recent files are kept before overwriting the oldest.
– This number can be changed in the log4j.xml file
§ Knowledge base:
– https://ping.force.com/Support/PingIdentityKnowledge
Home
– Tracking ID
– Session Cross-reference ID
– Not reference ID
http://documentation.pingidentity.com/display/PF610/Using+the+Server+Log+Filter
splunk-audit.log
Detailed Analysis