When pki CLI terminates SSL connection from PKI server, the server generates an audit log with empty ClientIP and ServerIP fields:
0.http-bio-8443-exec-3 - [13/Apr/2017:18:28:30 CEST] [14] [6] [AuditEvent=ACCESS _SESSION_TERMINATED][ClientIP=][ServerIP=][SubjectID=][Outcome=Success][Info=CLO SE_NOTIFY] access session terminated
The reason is the server obtained the client and server IP addresses from the following methods which do return null if the socket has already been closed:
Possible solutions:
Metadata Update from @mharmsen: - Custom field component adjusted to General - Custom field feature adjusted to '' - Custom field origin adjusted to Community - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field type adjusted to defect - Custom field version adjusted to '' - Issue priority set to: --- - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Metadata Update from @mharmsen: - Issue priority set to: critical (was: ---) - Issue set to the milestone: 10.4 (was: 0.0 NEEDS_TRIAGE)
Proposed fix based on option #1: https://review.gerrithub.io/#/c/357375/
Metadata Update from @edewata: - Issue assigned to edewata
Fixed in master: 749c137b59a9725a4cacdcd191b7e931303981df
Metadata Update from @edewata: - Issue close_status updated to: fixed - Issue set to the milestone: 10.4.2 (was: 10.4) - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Issue set to the milestone: 10.4.3 (was: 10.4.2)
Metadata Update from @mharmsen: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1446874
Issue linked to Bugzilla: Bug 1446874
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/2762
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.