#3012 [RFE] Substitutions of the certificate subject DN field only works for common name
Closed: migrated by dmoluguw. Opened by mharmsen.

When creating a custom CA profile trying to substitute anything other than request.req_subject_name.cn it does not get replaced with the appropriate value from the CSR.

Steps to Reproduce:

1. Create a cert profile with a custom subject DN like:
policyset.serverCertSet.1.default.params.name=CN=$request.req_subject_name.cn$, OU=$request.req_subject_name.ou$
2. Create a CSR containing CN=test.example.com, OU=foo
3. Sign the CSR

Actual results:

The resultning signed cert contains the CN=test.example.com, OU=$request.req_subject_name.ou$

Expected results:

The certificate subject should be populated with $request.req_subject_name.<field> for example: CN=test.example.com, OU=foo

Additional info:

This applies to other fields as well, such as $request.req_subject_name.sn$ and $request.req_subject_name.st$

Per 10.5.x/10.6 Triage: 10.6

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=1533469
- Custom field type adjusted to None
- Custom field version adjusted to None

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

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)

Metadata