if the goal is to have a single snap making use of the kerberos ticket,
as a workaround you can put something like this in /etc/krb5.conf
[libdefaults]
default_ccache_name =
DIR:/home/%{username}/snap/firefox/common/.cache/.k5_ccache
the default connections for the firefox snap prevent it to read hidden files
under $HOME, so we help it a little. Seems to work so far
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1849346
Title:
[snap] kerberos GSSAPI no longer works after deb->snap transition
Status in Mozilla Firefox:
New
Status in chromium-browser package in Ubuntu:
Confirmed
Status in firefox package in Ubuntu:
Confirmed
Bug description:
I configure AuthServerWhitelist as documented:
https://www.chromium.org/developers/design-documents/http-
authentication
and can see my whitelisted domains in chrome://policy/
but websites that used to work with SPNEGO/GSSAPI/kerberos no longer
work. I'm guessing the snap needs some sort of permission to use the
kerberos ticket cache (or the plumbing to do so doesn't exist...).
I can confirm that Chrome has the desired behavior.
To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1849346/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
