Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
I have a cluster of two nodes (dash-02 and dash-03) with a virtual IP address (rg-206). Each node has a keytab with it's principal and the principal for the virtual IP. I set "GSSAPIStrictAcceptorCheck no" in /etc/ssh/sshd_config on both nodes so I can ssh to the virtual IP's name and still authenticate with Kerberos.
This all works correctly when I set up and start authenticating.
[root@dash-01 tmp]# kinit testmonkey
Password for testmonkey:
[root@dash-01 tmp]# klist
Ticket cache: FILE:/tmp/krb5cc_0
Default principal: testmonkey
Valid starting Expires Service principal
01/19/12 15:47:04 01/20/12 15:47:04 krbtgt/EXAMPLE.COM
renew until 01/19/12 15:47:04
[root@dash-01 tmp]# ssh -l testmonkey dash-02 uname -n
dash-02
[root@dash-01 tmp]# ssh -l testmonkey dash-03 uname -n
dash-03
[root@dash-01 tmp]# ssh -l testmonkey rg-206 uname -n
dash-03
When I relocate the service to dash-02 authentication fails to rg-206.
[root@dash-01 tmp]# ssh -l testmonkey rg-206 uname -n
testmonkey@rg-206's password:
dash-02
Version-Release number of selected component (if applicable):
openssh-5.3p1-70.el6.x86_64
How reproducible:
Easily
Steps to Reproduce:
0. Start with three nodes and a virtual IP
1. Create a Kerberos realm on node 1
2. Create a two node cluster on nodes 2 and 3 w/ virtual IP
2. Set "GSSAPIStrictAcceptorCheck no" in /etc/ssh/sshd_config on cluster nodes
3. Copy ssh host keys from node 2 to node 3
4. Create keytab for node 2 including principals for node 2 and virtual IP
5. Create keytab for node 3 including principals for node 3 and virtual IP
6. Create user principal and user on all nodes
7. kinit user
8. ssh -l user virtual IP
9. relocate virtual IP to other node
10. ssh -l user virtual IP
Actual results:
ssh asks for a password on the second node after IP is relocated to it
Expected results:
ssh should not ask for a password regardless of where the virtual IP is located.
Additional info:
Comment 2RHEL Program Management
2012-05-03 05:18:12 UTC
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Is it still the case for RHEL7/Fedora? This is most probably not going to be fixed in RHEL6, since it was not a big deal during last 5 years, but if it is something that you are interested in or you have a customer for, please, provide a debug logs, that might give us some more information about the issue.
Otherwise I will close this bug.
Description of problem: I have a cluster of two nodes (dash-02 and dash-03) with a virtual IP address (rg-206). Each node has a keytab with it's principal and the principal for the virtual IP. I set "GSSAPIStrictAcceptorCheck no" in /etc/ssh/sshd_config on both nodes so I can ssh to the virtual IP's name and still authenticate with Kerberos. This all works correctly when I set up and start authenticating. [root@dash-01 tmp]# kinit testmonkey Password for testmonkey: [root@dash-01 tmp]# klist Ticket cache: FILE:/tmp/krb5cc_0 Default principal: testmonkey Valid starting Expires Service principal 01/19/12 15:47:04 01/20/12 15:47:04 krbtgt/EXAMPLE.COM renew until 01/19/12 15:47:04 [root@dash-01 tmp]# ssh -l testmonkey dash-02 uname -n dash-02 [root@dash-01 tmp]# ssh -l testmonkey dash-03 uname -n dash-03 [root@dash-01 tmp]# ssh -l testmonkey rg-206 uname -n dash-03 When I relocate the service to dash-02 authentication fails to rg-206. [root@dash-01 tmp]# ssh -l testmonkey rg-206 uname -n testmonkey@rg-206's password: dash-02 Version-Release number of selected component (if applicable): openssh-5.3p1-70.el6.x86_64 How reproducible: Easily Steps to Reproduce: 0. Start with three nodes and a virtual IP 1. Create a Kerberos realm on node 1 2. Create a two node cluster on nodes 2 and 3 w/ virtual IP 2. Set "GSSAPIStrictAcceptorCheck no" in /etc/ssh/sshd_config on cluster nodes 3. Copy ssh host keys from node 2 to node 3 4. Create keytab for node 2 including principals for node 2 and virtual IP 5. Create keytab for node 3 including principals for node 3 and virtual IP 6. Create user principal and user on all nodes 7. kinit user 8. ssh -l user virtual IP 9. relocate virtual IP to other node 10. ssh -l user virtual IP Actual results: ssh asks for a password on the second node after IP is relocated to it Expected results: ssh should not ask for a password regardless of where the virtual IP is located. Additional info: