Hi Nathan! Thanks for looking into this. In a working Kerberos setup, you won't need to enter any credentials. The browser can use the user's Kerberos ticket available in the system to authenticate against the webserver. So when you get asked for credentials it's a sign that Kerberos is _not_ working.
Maybe the information in the Bugzilla issue I created a few years ago (https://bugzilla.mozilla.org/show_bug.cgi?id=1734791) can be of help in tackling the issue. See my description and some of the comments for additional information and workarounds people found. I'm happy to test any Firefox snaps with proposed fixes! -- 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: In Progress Status in firefox package in Ubuntu: In Progress 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 : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
