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 1502533 - Changing cert-find to go through the proxy instead of using the port 8080
Summary: Changing cert-find to go through the proxy instead of using the port 8080
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-16 07:51 UTC by Thorsten Scherf
Modified: 2020-12-14 10:31 UTC (History)
7 users (show)

Fixed In Version: ipa-4.5.4-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 16:48:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0918 0 None None None 2018-04-10 16:49:12 UTC

Description Thorsten Scherf 2017-10-16 07:51:08 UTC 
This bug is created as a clone of upstream ticket:
https://pagure.io/freeipa/issue/6966

The cert-find backend is hardcoded to use port 8080 in dogtag.py. If the CA is on another master then port 8080 needs to be open in order to make a connection. This needs to be documented, perhaps on the ipa-server-install output.

This seems to also affect displaying a user (timing out) but I didn't investigate that part.
Comment 7 Nikhil Dehadrai 2018-01-17 08:00:20 UTC 
ipa-server version: ipa-server-4.5.4-8.el7.x86_64

VERIFIED the bug on the basis of following observations:

A) VERIFIED that, on RHEL 7.4.z IPA MASTER and CLIENT when the ports 8080 are blocked then 'ipa cert-find' command fails 

(ipa-server-4.5.0-22.el7_4.x86_64) (Reproducer)

IPA-Master:
-----------
# iptables -A OUTPUT -p tcp -o lo --dport 8080 -j DROP
# iptables -A OUTPUT -p tcp -i lo --dport 8080 -j DROP
# iptables -A OUTPUT -p tcp -o enp4s0 --dport 8080 -j DROP
# iptables -A INPUT -p tcp -i enp4s0 --dport 8080 -j DROP

[root@qe-blade-09 ~]# iptables -L --line-numbers
Chain INPUT (policy ACCEPT)
num  target     prot opt source               destination         
1    DROP       tcp  --  anywhere             anywhere             tcp dpt:webcache
2    DROP       tcp  --  anywhere             anywhere             tcp dpt:webcache

Chain FORWARD (policy ACCEPT)
num  target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
num  target     prot opt source               destination         
1    DROP       tcp  --  anywhere             anywhere             tcp dpt:webcache
2    DROP       tcp  --  anywhere             anywhere             tcp dpt:webcache


IPA-CLIENT:
--------------
[root@ipaqavmc ~]# kdestroy
[root@ipaqavmc ~]# kinit admin
Password for admin: 
[root@ipaqavmc ~]# ipa cert-find
ipa: ERROR: Certificate operation cannot be completed: Unable to communicate with CMS ([Errno 110] Connection timed out)

B) VERIFIED that, on RHEL 7.5 IPA MASTER and CLIENT (ipa-server-4.5.4-8.el7.x86_64) (Fix) when the ports 8080 are blocked then 'ipa cert-find' command is successful. The 'ipa cert-find' command eventually fails when both '8080' and '80' ports are blocked.

Thus on the basis of above observations and comment#5 and comment#6, marking the status of bug to 'VERIFIED'.
Comment 10 errata-xmlrpc 2018-04-10 16:48:21 UTC 
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-2018:0918
Note You need to log in before you can comment on or make changes to this bug.