RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

Commit dd47cfc removed the ability
to set pki_req_ext_oid and pki_req_ext_data in the pkispawn config.
This results in the --external-ca-profile option never setting the
requested values in the CSR (the default V1 template type specifying
"SubCA" is always used).


Version-Release number of selected component (if applicable): 4.8.0


How reproducible: always


Steps to Reproduce:
1. ipa-server-install --external-ca --external-ca-type ms-cs --external-ca-profile NotTheDefault



Actual results:

Observe that the wrong template extension data appears in /root/ipa.csr


Expected results:

Correct template extension data appears in /root/ipa.csr as specified via --external-ca-profile option.


Additional info:

Fix available on upstream ipa-4-8 branch:

- 71af731b3069fa1b2c0b51a3b917b5bc4da54350 Fix use of incorrect variable
- e632b220798833bcd65c6b266610c800ed0914d7 install: fix --external-ca-profile option

These were merged as part of PR https://github.com/freeipa/freeipa/pull/3410,
which added additional tests for the --external-ca-profile option (the new tests
revealed the regression).

ipa-4-8:

    d0d29cc move MSCSTemplate classes to ipalib
    e632b22 install: fix --external-ca-profile option
    71af731 Fix use of incorrect variable
    83ed057 Add more tests for --external-ca-profile handling
    a627df8 Collapse --external-ca-profile tests into single class
    740964c ci: add --external-ca-profile tests to nightly
    011c528 ci: add --external-ca-profile tests to gating

Automation test passed. Marking the bug as verified.

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.

https://access.redhat.com/errata/RHBA-2019:3348