When a Dogtag server is acting as a client of HTTS or TLS, it needs to audit "initiation, termination, and failure" of the sessions.
Metadata Update from @cfu: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1523330 - Custom field type adjusted to None - Custom field version adjusted to None - Issue priority set to: critical - Issue set to the milestone: 10.5
Metadata Update from @mharmsen: - Issue assigned to edewata
Per 10.5.x/10.6 Triage: 10.5
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 10.5)
Metadata Update from @cfu: - Issue assigned to cfu (was: edewata)
commit 261222b3451028d907a6a239c4bc12c85130f830 Author: Christina Fu cfu@redhat.com Date: Wed Aug 22 18:12:06 2018 -0700
ticket #2879 audit events for CA acting as TLS client This patch provides code for ticket 2879, adding audit events for CS when acting as a TLS client. For a running CS system, there are two cases when this happens: 1. When one CS subsystem is talking to another CS subsystem In this case: HttpClient is used 2. When a CS subsystem is talking to an ldap syste In this case: PKISocketFactory is used Events added are: - LOGGING_SIGNED_AUDIT_CLIENT_ACCESS_SESSION_ESTABLISH_FAILURE - LOGGING_SIGNED_AUDIT_CLIENT_ACCESS_SESSION_ESTABLISH_SUCCESS - LOGGING_SIGNED_AUDIT_CLIENT_ACCESS_SESSION_TERMINATED https://pagure.io/dogtagpki/issue/2879 Change-Id: Ib8e4c27c57cb2b13b461c36f37f52dc6a13956f8
Metadata Update from @cfu: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5.13 (was: 10.6)
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/2998
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.