Red Hat Bugzilla – Bug 1541853
ProfileService: config values with backslashes have backslashes removed
Last modified: 2018-04-10 13:04:28 EDT
Description of problem:
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.
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.
How reproducible: always
Steps to Reproduce:
1. create profile config with SubjectNameDefault configuration with escaped comma (see example above).
the /raw method must be used
2. attempt to issue a certificate using that profile
Certificate issuance fails because the backslash got removed upon profile
configuration import, resulting in an unparsable DN.
Backslash does not get clobbered on profile import, and certificate issuance
Pushed to upstream master: e634316eb7f2aedc65fe528fb572b15e1bdc1eb2
RHEL 7 JUSTIFICATION
The PKI Team is working on obtaining Common Criteria certification for the RHCS layered product. Several of the components that comprise this release are now located within RHEL 7. As such, the following bug has been identified as a worthy candidate for inclusion for this release, and so we are requesting an exception flag ACK so that we may attempt to include this bug within the snapshot phases.
I tested this Bugzilla on a 10.5.1-7.el7 version.
Steps which I followed to verify the Bugzilla:
- Get profile caServerCert in raw format.
- Change the Id of the profile. Modify the attribute `default.params.name` to `CN\=$request.req_subject_name.cn$,O\=Red Hat\, Inc.`
- Add the profile to the CA and Enable it.
- Show the profile in raw format. Make sure that `default.params.name` attribute value does not contain the backslash.
- Issued the certificate using the profile, and it is successful.
Verifying this bug.
*** Bug 1346433 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.