+++ This bug was initially created as a clone of Bug #1017292 +++ Description of problem: When installed on Fedora, krb5-auth-dialog will run with the --auto command on every graphical desktop session. The --auto command causes krb5-auth-dialog to exit if there is no credential cache available. Bug 1017292 describes a special situation where this can be fixed by checking for the KRB5CCNAME environment variable. However, there are other situations where the --auto flag leads to erroneous, unexpected behavior which are not fixed by the patch in bug 1017292. For example, I am using local Linux login here (not using Kerberos authentication for my Linux system) but I am still in an AD environment and using kerberos heavily to access windows-based resources. Thus I put krb5-auth-dialog.desktop in my autostart folder and use it to enter my AD credentials after login. This worked fine up to F19. In F20 it ceased to work because of the --auto flag. However, there are circumstances (such as when using KEYRING:persistent caches) where the KRB5CCNAME variable may be set, but the cache contents are not yet stored (such as SSSD with offline authentication). krb5-auth-dialog should check whether the KRB5CCNAME variable has been set in the environment and not exit if it is. Version-Release number of selected component (if applicable): krb5-auth-dialog-3.2.1-7.fc20.x86_64 How reproducible: Every time Steps to Reproduce: 1. Use a configuration with local Unix accounts in an AD environment, where Kerberos is used nevertheless to authenticate against AD servers 2. Configure krb5-auth-dialog to be autostarted using gnome-tweak-tool or gnome-session-properties 3. Log in to a graphical session Actual results: krb5-auth-dialog is not running when the desktop comes up. Expected results: krb5-auth-dialog should be running and inform the user that their credential cache is expired. Additional info: In short, the --auto flag in the krb5-auth-dialog.desktop file is bogus. It assumes that a kerberos authentication environment always has to be present when krb5-auth-dialog is used, which is not the case. Moreover, I fail to understand what problem the use of the --auto flag in the startup file is supposed to solve. IMO removing it would do no harm to anybody.
I should have deleted the 5th paragraph ("However, ... if it is.", which comes from bug 1017292) from the bug description. Please ignore it. Sorry.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.