I don’t have a solution pattern for this at present. But maybe if I explain what has changed someone who understands how to do browser proxying can point us in the right direction for a fix.
Previously the Sensu Core API did not enforce authentication and the addon uchiwa dashboard implemented authentication using manually configurable access tokens, which made it possible to cache as you have been doing.
The big change here is Sensu Go API now requires authentication using JWT, using short lived generated access tokens and a refresh tokens that can be used to request a new token. There’s no way to disable the authentication requirement nor a way to set a manual static access_token so that you can use the web server as an authentication proxy.
I think the way forward here is to make use of Sensu Go support for both LDAP and OIDC authentication directly. The official binaries have bpth LDAP and OIDC authentication built in as enterprise features. You should be able to integrate Sensu directly with your kerberos using the LDAP support.
And as per the new updated pricing policy, starting with Sensu Go 5.15 all the enterprise features will be available for use in the official binaries without needing a license (for deployments with less than 100 entities).
Watch for a release announcement next week for Sensu Go 5.15 availability.