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.
Bug 1080865 - Proxy change required on Master IPA Server to allow IPA Replica when using Dogtag
Summary: Proxy change required on Master IPA Server to allow IPA Replica when using Do...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: rc
: ---
Assignee: Martin Kosek
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks: 1083878
TreeView+ depends on / blocked
 
Reported: 2014-03-26 09:08 UTC by Martin Kosek
Modified: 2014-06-18 00:15 UTC (History)
2 users (show)

Fixed In Version: ipa-3.3.3-27.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1083878 (view as bug list)
Environment:
Last Closed: 2014-06-13 13:07:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Martin Kosek 2014-03-26 09:08:53 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/4265

This ticket is being filed to address the changes that are a part of the following Dogtag ticket:
* [https://fedorahosted.org/pki/ticket/816 pki-tomcat cannot be started after installation of ipa replica with ca]

Basically, the Dogtag change requires the Dogtag Clone's SSL Server certificate (located on the IPA Replica) to be issued by its associated Dogtag Master (located on the IPA Master).

Basically, the following change needs to take place in the IPA Master's '/etc/httdp/conf.d/ipa-pki-proxy.cfg' file.  Change:

  # matches for ee port
  <LocationMatch "^^/ca/ee/ca/checkRequest|^^/ca/ee/ca/getCertChain|^^/ca/ee/ca/getTo
  kenInfo|^^/ca/ee/ca/tokenAuthenticate|^^/ca/ocsp|^^/ca/ee/ca/updateNumberRange|^^/ca
  /ee/ca/getCRL">
      NSSOptions +StdEnvVars +ExportCertData +StrictRequire +OptRenegotiate
      NSSVerifyClient none
      ProxyPassMatch ajp://localhost:8009
      ProxyPassReverse ajp://localhost:8009
  </LocationMatch>

to:

  # matches for ee port
  <LocationMatch "^^/ca/ee/ca/checkRequest|^^/ca/ee/ca/getCertChain|^^/ca/ee/ca/getTo
  kenInfo|^^/ca/ee/ca/tokenAuthenticate|^^/ca/ocsp|^^/ca/ee/ca/updateNumberRange|^^/ca
  /ee/ca/getCRL'''|^^/ca/ee/ca/profileSubmit'''">
      NSSOptions +StdEnvVars +ExportCertData +StrictRequire +OptRenegotiate
      NSSVerifyClient none
      ProxyPassMatch ajp://localhost:8009
      ProxyPassReverse ajp://localhost:8009
  </LocationMatch>
Comment 2 Martin Kosek 2014-03-26 09:16:55 UTC 
Fixed upstream:

master: https://fedorahosted.org/freeipa/changeset/6ecc4600e9370a637916360396f18699e4b7f59b/
ipa-3-3: https://fedorahosted.org/freeipa/changeset/8e8a020f8d2476cca321349fa24db4bee95270d8/
Comment 4 Martin Kosek 2014-03-26 13:51:10 UTC 
QE instructions - we can verify as SanityOnly and just make sure that replica installation with CA (--setup-ca/ipa-ca-install) still works.

You can also verify the change by making sure that the missing URI is in the IPA PKI proxy configuration:

# grep /ca/ee/ca/profileSubmit /etc/httpd/conf.d/ipa-pki-proxy.conf
Comment 5 Namita Soman 2014-03-26 16:14:37 UTC 
using ipa-server-3.3.3-25.el7.x86_64
# grep /ca/ee/ca/profileSubmit /etc/httpd/conf.d/ipa-pki-proxy.conf

# grep profileSubmit /etc/httpd/conf.d/ipa-pki-proxy.conf
<LocationMatch "^/ca/agent/ca/displayBySerial|^/ca/agent/ca/doRevoke|^/ca/agent/ca/doUnrevoke|^/ca/agent/ca/updateDomainXML|^/ca/eeca/ca/profileSubmitSSLClient">


verified update with ipa-server-3.3.3-27.el7.x86_64
# grep /ca/ee/ca/profileSubmit /etc/httpd/conf.d/ipa-pki-proxy.conf
<LocationMatch "^/ca/ee/ca/checkRequest|^/ca/ee/ca/getCertChain|^/ca/ee/ca/getTokenInfo|^/ca/ee/ca/tokenAuthenticate|^/ca/ocsp|^/ca/ee/ca/updateNumberRange|^/ca/ee/ca/getCRL|^/ca/ee/ca/profileSubmit">

And ran installs using ipa-server-3.3.3-27.el7.x86_64:
automated test output for replica installation with CA:
:: [   PASS   ] :: Running ' /usr/sbin/ipa-replica-install -U --setup-ca --setup-dns --forwarder=x.x.x.x -w <password> -p <password> /opt/rhqa_ipa/replica-info-cloud-qe-18.testrelm.test.gpg' (Expected 0, got 0)


automated tests passed for ipa-ca-install
:: [   PASS   ]   Installing CA Replica with --no-host-dns option
:: [   PASS   ]   Installing CA Replica without --no-host-dns option
:: [   PASS   ]   Installing CA Replica with --skip-schema-check option
Comment 6 Martin Kosek 2014-04-03 07:06:46 UTC 
This change will be also required in RHEL-6.6 so that PKI replicas can be spawned. Until this is fixed in RHEL-6.x, manual change to ipa-pki-proxy.conf + restart of httpd is needed.

I will clone this bug.
Comment 7 Ludek Smid 2014-06-13 13:07:28 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.