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 1430253 - [RFE] IPA does not support alternative IPs/DNS-Names for ssh login
Summary: [RFE] IPA does not support alternative IPs/DNS-Names for ssh login
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.3
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-08 08:02 UTC by Andrey Bondarenko
Modified: 2020-05-14 15:43 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-16 17:17:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Andrey Bondarenko 2017-03-08 08:02:23 UTC
Description of problem:

The file "/etc/ssh/ssh_known_hosts" supports multiple, comma seperated values for DNS-Names and IPs, so that one can associate multiple names/IPs with one host key. 

The FreeIPA should support host aliases and SSSD should support adding aliases into the output of the sss_ssh_knownhostsproxy so that one could use either connect to samplehost.example.com and samplehost.linux.example.com

How reproducible:

   always

Comment 2 Jan Cholasta 2017-03-14 11:08:07 UTC
Note that this already works as long as you use the canonical host name for the IPA host:

$ host a.example.com
a.example.com has address 1.2.3.4
$ host b.example.com
b.example.com has address 1.2.3.4
$ host 1.2.3.4
4.3.2.1.in-addr.arpa domain name pointer a.example.com.
$ ipa host-show a.example.com
<...>
$ ipa host-show b.example.com
ipa: ERROR: b.example.com: host not found
$ ssh a.example.com
<works>
$ ssh b.example.com
<works>

Comment 4 Petr Vobornik 2017-03-17 16:00:19 UTC
Upstream ticket:
https://pagure.io/freeipa/issue/6779

Comment 7 Amy Farley 2019-08-16 17:17:27 UTC
I am going to close this bz and let the UPSTREAM work continue.


Note You need to log in before you can comment on or make changes to this bug.