#3216 Relative path for configFile in ACME configuration
Closed: migrated 3 years ago by dmoluguw. Opened 3 years ago by edewata.

Currently the configFile parameters in some ACME configuration files will only work with absolute paths. Ideally it should work with paths relative to the instance directory. For example, the following relative path:

configFile=conf/ca/CS.cfg

should be equivalent to this absolute path under the instance directory:

configFile=/var/lib/pki/pki-tomcat/conf/ca/CS.cfg

or this path under /etc directory which is linked from the instance directory:

configFile=/etc/pki/pki-tomcat/ca/CS.cfg

Metadata Update from @pingou:
- 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 type adjusted to None
- Custom field version adjusted to None

3 years ago

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/3333

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata