(In reply to Mantas Mikulėnas (grawity) from comment #6) > The magic environment variables to reveal such problems are > `KRB5_TRACE=/dev/stderr NSPR_LOG_MODULES=negotiateauth:5`.
This worked for me on Snap version `125.0.2-1` but I got no output on version `131.0-1`. After some digging (https://bugzilla.mozilla.org/show_bug.cgi?id=1275744) I found that `NSPR_LOG_MODULES` had changed to `MOZ_LOG`. So, in total: `KRB5_TRACE=/dev/stderr MOZ_LOG=negotiateauth:5`. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox 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 snapd: New Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: Triaged 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
