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 1602087 - Would like to use aliases or load balanced addresses to access the IPA API
Summary: Would like to use aliases or load balanced addresses to access the IPA API
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: ipa
Version: ---
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: rc
: 8.0
Assignee: Thomas Woerner
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-17 19:09 UTC by Marc Richter
Modified: 2023-09-14 04:31 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-14 11:28:48 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Marc Richter 2018-07-17 19:09:16 UTC 
Description of problem:  We would like to use aliases or load balanced addresses to access the IPA API, but when we do so there is always an error about the http referrer. It's not ideal for us to hard code single point of failure servers into our code, so we are looking for a workaround.

    Error when attempting to use API with "ipa.x.example.com"
    Traceback (most recent call last):
     File "/n/tech/python/tech/pdtsys/unix/generate_k5logins.py", line 19, in
    <module>
       prodid_group = ipa.group_show('production_id')
     File "/n/tech/python/tech/pdtsys/unix/ipa.py", line 106, in group_show
       raise err

    RuntimeError: Missing or invalid HTTP Referer,


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


How reproducible: Attempt to access the IPA API using an alias or F5


Actual results: Error: Missing or invalid HTTP Referer


Expected results: Successful access to the API


Additional info: From mailing list: using multiple frontends for IPA API is not
supported yet. Disabling HTTP_REFERER will cause numerous security
issues.

I have https://github.com/abbra/freeipa/pull/9 which is a work in
progress to add ability to manually configure list of aliases. However,
it requires changes to the core of IPA framework and there was no
priority for it for about a year.
Comment 3 Rob Crittenden 2018-07-17 19:23:57 UTC 
Since you have your own client code you can look up the DNS SRV ldap records to find all the IPA masters for the domain and use those to iterate/load balance over.
Comment 4 Armando Biagioni Neto 2018-08-06 14:57:19 UTC 
Upstream ticket:
https://pagure.io/freeipa/issue/7665
Comment 6 Petr Čech 2019-12-11 18:50:57 UTC 
We will provide recommended approach how to load balance our solutions.
Comment 14 Petr Čech 2020-07-14 11:28:48 UTC 
Thank you taking your time and submitting this request for Red Hat Enterprise Linux. The request was cloned to the upstream tracker a long time ago (see link to the upstream ticket above), but it was unfortunately not given priority either in the upstream project, nor in Red Hat Enterprise Linux.

Given that this request is not planned for a close release, it is highly unlikely it will be fixed in this major version of Red Hat Enterprise Linux. We are therefore closing the request as WONTFIX.

To request that Red Hat reconsiders the decision, please reopen the Bugzilla with the help of Red Hat Customer Service and provide additional business and/or technical details about it's importance to you. Please note that you can still track this request or even offer help in the referred upstream Pagure ticket to expedite the solution.
Comment 15 Red Hat Bugzilla 2023-09-14 04:31:33 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.