There may be desire to not record complete key archival request records in ldap. We should look into possible feature enhancements such as: a. option to disable KRA request records writes to ldap b. option to write only partial KRA request records to ldap
commit e621767763207728de7d2133c5b43718ec528c0a Author: Christina Fu cfu@redhat.com Date: Tue Apr 5 11:44:00 2016 -0700
Ticket #2271 TMS- clean up key archival request records in ldap This patch does the following: - it adds in the kra request an extra field called "delayLDAPCommit" - when the request comes in to be processed, it sets this field to "false" - by default, if this field does not exist, the updateRequest() method will just write to ldap, just like before; however, if this field exists and it contains "true" then it will delay the write - once the request is processed and all unwanted fields are cleared from the request record, it will set "delayLDAPCommit" to "false", and call updateRequest(), which will then do the actual write to ldap - In addition, I also screened through both KRA and TPS code and removed debug messages that contain those fields.
This ticket deals with TMS only. A separate ticket will be open for non-TMS.
reopen to accommodate 2nd part to shrink logs (no need to open another ticket).
commit 897fd14bfdfa4cd722f95ba60c8dd7a9eaa37219 Author: Christina Fu cfu@redhat.com Date: Thu Jun 2 16:47:24 2016 -0700
Ticket #2271 Part2:TMS:removing/reducing debug log printout of data This patch comments out unneeded data in TMS debug logs (TPS&TKS); It reduces the size of the debug logs by a lot. Note that for ease of later development debugging, the debug lines are commented out instead of being removed
Metadata Update from @cfu: - Issue assigned to cfu - Issue set to the milestone: 10.3.2
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/2391
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.