You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been seeing issues when running a single Grafana instance and signing in with basic auth. Signing in will work fine, but when the instance is restarted grafana-kiosk will be kicked back to the sign in page, but it will not try to sign in. The solution right now is to restart grafana-kiosk, but I feel like there may be a simpler solution to this problem.
The text was updated successfully, but these errors were encountered:
This is a general problem, if the instance restarts and you lose your credentials (session token expires), the browser is sent back to the login screen.
Right now it's just infinitely waiting for the process to be killed.
The kiosk could inspect page loads and try to detect the login page.
There's the other issue of the session token expiring (and the grafana instance hasn't restarted), which also sends you back to the login page. Setting a long timeout on the expiration can alleviate it, but it's not a great fix.
Detecting the login would solve both problems, but may cause some undesirable load on the kiosk. I'll have to see what the impact it will cause, and maybe just add a new flag to enable it.
made progress on this and also discovered a bug that will help with performance, will get a new release out that addresses cpu utilization, then add the re-login code.
@briangann have you been able to make some progress on this? It's not really a super critical issue as we do not experience this too often but it happens at times.
I have been seeing issues when running a single Grafana instance and signing in with basic auth. Signing in will work fine, but when the instance is restarted grafana-kiosk will be kicked back to the sign in page, but it will not try to sign in. The solution right now is to restart grafana-kiosk, but I feel like there may be a simpler solution to this problem.
The text was updated successfully, but these errors were encountered: