#2865 X500Name.directoryStringEncodingOrder overridden by CSR encoding
Closed: fixed Opened by mharmsen.

Would like the ability to override CSR encoding based on X500Name.directoryStringEncodingOrder setting. Specifically when specifying subject DN to be encoded as printableString.


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 rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1471935
- Custom field type adjusted to None
- Custom field version adjusted to None

Per 10.5.x/10.6 Triage: 10.5

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

Author: Christina Fu cfu@redhat.com
Date: Tue Jun 12 11:47:57 2018 -0700

Ticket 2865 X500Name.directoryStringEncodingOrder overridden by CSR encoding
This patch allows profile to have control over whether to override the subjectDN
encoding in the CSR with the encoding set by the system.
New parameter in profile:
policyset.<policy set>.<#>.default.params.useSysEncoding=true
where "true" means to override the subjectdn with the system default order or
the order set by X500Name.directoryStringEncodingOrder in CS.cfg
by default, without useSysEncoding in profile, it is treated as false.
fixes https://pagure.io/dogtagpki/issue/2865
Change-Id: I41f8f5371f26668909624f056a77ffbf66f0f5e1

Metadata Update from @mharmsen:
- Custom field fixedinversion adjusted to pki-core-10.5.10-1.fc27
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5.10 (was: 10.5)

Coverity changes checked into master:

commit adbeb1cb12e835628d94c10f5b99573a3f6fff68
Merge: 3ccfeea19 ef1fe72a7
Author: mharmsen99 mharmsen@redhat.com
Date: Wed Sep 19 11:01:06 2018 -0600

Merge pull request #48 from mharmsen99/ticket-2865
X500Name.directoryStringEncodingOrder overridden by CSR encoding

Metadata Update from @mharmsen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1471935, https://bugzilla.redhat.com/show_bug.cgi?id=1629048 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1471935)

Metadata Update from @mharmsen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1471935,https://bugzilla.redhat.com/show_bug.cgi?id=1629048 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1471935, https://bugzilla.redhat.com/show_bug.cgi?id=1629048)

Metadata Update from @mharmsen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1471935 https://bugzilla.redhat.com/show_bug.cgi?id=1629048 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1471935,https://bugzilla.redhat.com/show_bug.cgi?id=1629048)

Metadata Update from @mharmsen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1471935,https://bugzilla.redhat.com/show_bug.cgi?id=1629048 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1471935 https://bugzilla.redhat.com/show_bug.cgi?id=1629048)

Check-in for this issue was made in 10.5.10
Coverity fix for this issue was made in 10.6

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5.13 (was: 10.5.10)

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5.10 (was: 10.5.13)

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5.13 (was: 10.5.10)

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

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