Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 1386262 - [RFE] Support kerberized SSH as an alternative to keys
Summary: [RFE] Support kerberized SSH as an alternative to keys
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: Adam Ruzicka
QA Contact: Peter Ondrejka
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On: 1386266
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-18 13:50 UTC by Daniel Lobato Garcia
Modified: 2019-09-26 16:17 UTC (History)
8 users (show)

Fixed In Version: tfm-rubygem-foreman_remote_execution_core-1.0.5
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:54:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 11936 0 None None None 2016-10-18 14:05:51 UTC

Description Daniel Lobato Garcia 2016-10-18 13:50:03 UTC
It'd be relatively easy for the proxy to use the existing krb5 infrastructure (used by GSS-TSIG DNS updates and Realm) as an optional alternative to SSH keys.

Comment 1 Daniel Lobato Garcia 2016-10-18 13:50:07 UTC
Created from redmine issue http://projects.theforeman.org/issues/11936

Comment 2 Ivan Necas 2017-04-21 06:56:20 UTC
How does this BZ differ from https://bugzilla.redhat.com/show_bug.cgi?id=1386266 ?

Comment 3 Satellite Program 2017-05-25 10:15:03 UTC
Upstream bug assigned to aruzicka

Comment 4 Satellite Program 2017-05-25 10:15:07 UTC
Upstream bug assigned to aruzicka

Comment 5 Daniel Lobato Garcia 2017-05-26 15:01:35 UTC
This BZ is about reusing the information we have (keytab for Realms (https://theforeman.org/manuals/1.15/index.html#4.3.8Realm) or GSS TSIG (https://theforeman.org/manuals/1.15/index.html#4.3.8Realm)) to run jobs on hosts in that realm. This BZ cannot be closed without closing https://bugzilla.redhat.com/show_bug.cgi?id=1386266 first, as you'd need first the ability to run jobs via tokens to be able to use the keytabs I mentioned.

Comment 6 Satellite Program 2017-07-10 12:14:45 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/11936 has been resolved.

Comment 9 Peter Ondrejka 2018-02-07 17:56:58 UTC
Verified on Sat 6.3 snap 35 along with https://bugzilla.redhat.com/show_bug.cgi?id=1386266

Comment 10 Satellite Program 2018-02-21 16:54:17 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/RHSA-2018:0336


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