krb5-auth-dialog is a simple dialog that monitors Kerberos tickets, and pops up a dialog when they are about to expire. Eventually, we expect it to be part of GNOME. Configuration ============= Configuration settings are handled via gsettings. You can set the principal that is used to acquire tickets via: gsettings set org.gnome.KrbAuthDialog principal "principal@YOUR.REALM" You can set the time of the first password prompt via: gsettings set org.gnome.KrbAuthDialog prompt-minutes 30 You can set the principals pkinit identifier via: gsettings set org.gnome.KrbAuthDialog pk-userid "FILE:/path/to/user.pem,/path/to/user.key" or if you're using a smartcard: gsettings set org.gnome.KrbAuthDialog pk-userid "PKCS11:/usr/lib/opensc/opensc-pkcs11.so" DBus API ======== You can request a ticket granting ticket via DBus: dbus-send --print-reply --type=method_call \ --dest=org.gnome.KrbAuthDialog \ /org/gnome/KrbAuthDialog \ org.gnome.KrbAuthDialog.acquireTgt \ string:'principal' If the sent principal doesn't match the one currently in the ticket cache the request fails. To request a TGT for the "default" principal use string:''. See examples/tgt-signals.py for information about sent DBus signals. Plugins ======= Plugins are currently disabled by default. Individual plugins can be enabled via gsettings: Enable pam and dummy plugions: . gsettings set org.gnome.KrbAuthDialog.plugins enabled "['pam', 'dummy']" To list currently enabled plugins: gsettings get org.gnome.KrbAuthDialog.plugins enabled A Note on Translations ====================== Kerberos doesn't translate either its prompts or its error messages. As the prompt is very visible, we need to translate it externally. To do this, the etpo binary in etpo/ can be used to extract the public strings that Kerberos uses. We are checking that in for now, until Kerberos gets translated. If your language doesn't have a translation yet and you want to provide one do a cd po; make krb5-auth-dialog.pot in the unpacked source tree to get a template of translatable strings.