Comment 4 for bug 1970182

The workaround provided by Ronzo is much appreciated, but considering that this will mostly be relevant in larger environments with central authentication, keeping the cached credentials openly in the middle of the home directory may at least open support issues with users wondering what that file may be, deleting it, and so on.

We've also experimented with other paths and bind-mounting a dedicated ccache directory into the boundaries of the Snap, which either fails due to missing access permissions or the requirement to start Firefox with a different $KRB5CCNAME environment than the default.

If the Snap could access the krb5.conf(5) default default_ccache_name, that would be a huge step forward.