There are working alternatives that can be specified, like FILE and MEMORY, but not a fallback. If the cache is configured as KEYRING in krb5.conf, Kerberos will not fall back to anything else, it will just fail, without any clear indication as to why.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2139666 Title: Kerberos authentication does not work with KEYRING cache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2139666/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
