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:
when logged in to machine with Red Hat krb5.conf with username different than kerberos principal name, the krb5-auth-dialog keeps exiting silently until "kinit $principal" is run. Then it works normally until kdestroy is called. Changing "principal" option in preferences has no effect.
Version-Release number of selected component (if applicable):
krb5-auth-dialog-0.13-3.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. log in as user test
2. run krb5-auth-dialog. It exits immediately with $? = 0
3. run kinit $your_red_hat_nick
4. run krb5-auth-dialog - it works fine
Actual results:
Expected results:
If kinit returns "Couldn't acquire kerberos
ticket: 'Client not found in Kerberos database'"
the krb5-auth-dialog should pop up window asking for principal name in addition to password.
Similarly, if there are more realms configured, krb5-auth-dialog should give option which one it should kinit
Additional info:
Comment 2RHEL Program Management
2011-01-20 18:08:16 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. 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. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 3RHEL Program Management
2011-07-06 01:24:02 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. 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. If you would like it considered as an
exception in the current release, please ask your support
representative.
I could reproduce this on RHEL 6.2 anytime, and in my opinion this is a duplicate of the Fedora bug 672846 -- we are missing -A (or --always) when running krb5-auth-dialog.
One downside of using -A or --always is that the user will get a notification about expired network credentials even if they don't intend to use Kerberos at all and just happen to have krb5-auth-dialog installed. You could counter that by saying that the notification can be clicked away using "don't show me this again", or the package can be uninstalled.
After talking to Matěj, I am even more inclined to decline this (comment 9). I will reconsider this if there is an actual customer request. Otherwise, it doesn't make sense to tweak the UX with visible side-effects for RHEL 6.x at this stage.
Comment 14RHEL Program Management
2016-10-05 16:35:15 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.