wir haben seit längerem ein Raspi mit AlmaLinux am laufen. Auf diesem läuft ein Firefox im Kiosk mode mit welchem wir bis anhin ohne Probleme ein dashboard mit Autologin aufmachen konnten.
Dazu nutzen wir einen Automation user.
Seit dem letzten Update auf p17 funktioniert das automatische login nicht mehr.
Gestartet wird der Firefox (upgrade auf 115.5.0) mit
mit 2.3.0 wird die Option deprecated die Credentials im GET Parameter mitzugeben und in 2.5.0 komplett entfernt.
Da wir auch einige Firefox Kiosks auf Raspi Basis zum Anzeigen von Dashboards auf TVs verwenden würde mich interessieren ob jemand eine Idee hat wie ein Autologin zukünftig funktionieren kann, am besten ohne irgendwelche Firefox Plugins die einen Auth Header anhängen.
While I like Kiosks, I dislike the idea of sessions that last forever. So I would suggest this workaround:
First: Set the expiry (both idle and absolute) reasonably high.
Second: When a login should be needed, connect via SSH to the Kiosk device (here tunneling port 5900):
ssh -L 5900:localhost:5900 root@192.0.2.1
Then in the session start x11vnc mirroring the display:
x11vnc -localhost -auth guess
Then you can use any VNC client (I prefer remmina) to get the desktop (on localhost:0), log in, change settings… It should also be noted that for many sophisticated dashboards old RPi 1 and 2 are getting too slow. In this case run a xpra session on a faster machine in the background and only use the RPi to display the xpra session. Another advantage here is that you can pickup the xpra session from any machine to configure something or login.
Ping me if you need further details, I will write a small tutorial on xpra then.
@mschlenker, this is less than a bad workaround.
Kiosks do not work with manual login.
Grafana dashboards can be shown in Kiosk modes without any issues.
To clarify: Login not to the desktop session, but login to a web site in a browser. Checkmk is not the only application that does not provide endless sessions. And from time to time you need to configure things like the tab cycle extension. The big advantage of x11vnc here is to mirror the physical output – usually much more convenient than connecting a physical keyboard and mouse.
Please see the initial post. Using an RPi and autostarting a browser in a user session seems to be a very common approach to display Checkmk dashboards:
hey, would be nice to get an short tutorial from u:) we arent sure if this is really a solution for us but to understand it better we would love to hear from u:)
Put your browser into autostart (/etc/.config/autostart/filename.desktop)
In that file on section Exec add firefox -kiosk -private-window https://[FQDN HOSTNAME]/main/check_mk/login.py?&_origtarget=dashboard.py?name=public_01&_username=[AUTOMATION USERNAME]&_secret=[AUTOMATION USERSECRET]&_login=1 and that’s it.
There is nothing more to explain.
Yes before you do that of course, you need to have a user to log in. This username and password (unfortunately) need to go into the string above.
many thanks for the answer,
but wasn’t it noted that this solution will be removed?
and we had this solution running, but it doesn’t work anymore (yes we can reactivate it until checkmk 2.5, but we would like to have a long-term solution) - that’s why we asked @mschlenker how his solution works:P
