#2909 ProfileService: config values with backslashes have backslashes removed
Closed: fixed Opened by ftweedal.

When writing (importing, updating) RAW profile data, config values that have backslashes
in them have the backslashes dropped, leading to issuance failures or issuance of incorrect
certificates.

For example:

policyset.serverCertSet.1.default.params.name=CN=$request.req_subject_name.cn$, O=Red Hat\, Inc.

becomes:

policyset.serverCertSet.1.default.params.name=CN=$request.req_subject_name.cn$, O=Red Hat, Inc.

Which causes issuance failures due to parse failure of the resulting DN.


Metadata Update from @ftweedal:
- Issue assigned to ftweedal

Gerrit review: https://review.gerrithub.io/#/c/395433/

Metadata Update from @ftweedal:
- 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

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

Per email discussion with ftweedal, moving to 10.6.

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

Pushed to master: e634316eb7f2aedc65fe528fb572b15e1bdc1eb2

Metadata Update from @ftweedal:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1541853

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

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5.5 (was: 10.6)

Metadata Update from @mharmsen:
- Custom field fixedinversion adjusted to pki-core-10.5.5-1.fc27

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

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