#3029 profile CLI: inappropriate use of backslash escape breaks profile configuration
Closed: fixed Opened by ftweedal.

Using pki ca-profile-{edit,add,mod} --raw introduces backslashes into some profile configurations,
breaking the configuration. In particular, this occurs with colon (':') characters in values, which
can occur in IPAddressName values (and possibly other values).

This is due to the behaviour of java.util.Properties. The issue is similar to
https://pagure.io/dogtagpki/issue/2909.


Metadata Update from @mharmsen:
- 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
- Issue set to the milestone: 0.0 NEEDS_TRIAGE

Gerrit review: https://review.gerrithub.io/c/dogtagpki/pki/+/412719

Metadata Update from @ftweedal:
- Issue set to the milestone: None (was: 0.0 NEEDS_TRIAGE)

Metadata Update from @mharmsen:
- Issue set to the milestone: 0.0 NEEDS_TRIAGE

Fixed in master: dfa1b02ac6c2defc775cb0080214732d0613961d

Metadata Update from @ftweedal:
- Issue close_status updated to: fixed

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.6.4 (was: 0.0 NEEDS_TRIAGE)

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

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