I enable KRB5_TRACE as well to get more detailed logs for kerberos in firefox. ``` KRB5_TRACE=/dev/stderr NSPR_LOG_MODULES=negotiateauth:5 KRB5CCNAME=FILE:/tmp/krb5cc_1000 snap run firefox ```
It depends on how the website handles authentication. If a website requires kerberos authentication to get a session cookie and then reuses the session cookie for auth, then kerberos only happens initially and after reload cache. But Kerberos has its own authentication sessions with a service (i.e. website) so some websites won't handle a session themselves and let the kerberos session handle it from what I've seen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2138268 Title: Kerberos authentication slow in Firefox (snap) and Chromium (snap) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2138268/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
