While debugging the Standalone-DRM, I utilized the Tomcat Access Log.
It occurred to me that it might be useful from a development standpoint to be able to customize the log output during installation.
To do this, one would need to change this entry in server.xml from:
<Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" prefix="localhost_access_log." suffix=".txt" pattern="common" resolveHosts="false"/>
to:
<Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" prefix="localhost_access_log." suffix=".txt" pattern=[PKI_TOMCAT_ACCESS_LOG_PATTERN] resolveHosts="false"/>
by adding a new "slot" variable called [PKI_TOMCAT_ACCESS_LOG_PATTERN] whose value would be controlled by a new variable called pki_access_log_pattern located under the [Tomcat] section in /etc/pki/default.cfg file. The default value for this variable would be pki_access_log_pattern="common" which could be easily overridden in the user's default.cfg override file used during pkispawn installation/configuration to enable a developer to customize his/her access logs.
Syntax for the "pattern" parameter is described in detail in "http://tomcat.apache.org/tomcat-7.0-doc/config/valve.html".
NOTE: I originally also considered suggesting the ability to override the "className" parameter such that 'org.apache.catalina.valves.ExtendedAccessLogValve' could be substituted for 'org.apache.catalina.valves.AccessLogValve'. However, further research did not yield enough evidence to show that this feature would be all that useful, and indeed since the "pattern" syntax differs between the two valves, it would probably lead to greater confusion than it is worth.
This can be done without adding new deployment parameters: http://pki.fedoraproject.org/wiki/Custom_Installation#Customizing_Tomcat_access_log
Metadata Update from @mharmsen: - Issue set to the milestone: 10.3.1
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/1336
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.