Version 2.0.0 brings two of the most requested features – Multi-user support and authentication. As well as these 2 big new features the underlying Laravel framework has been updated 2 major versions, from 5.5 to 5.7.
Multi-user support and Authentication
If you do a new install or upgrade from a previous version a default Admin user is created. By default this admin user doesn’t require authentication and is the only account that can manage other users.
When you create a new user (or edit the Admin account) you have a few different options.
- You can choose not to set a password, if you do this then when switching to this user there will never be a password asked for, anyone can change items or settings, this makes most sense on a private intranet where you are the only person with access.
- You can set a password and leave the toggle enabled for making the front page public. This will mean when switching to the user anyone can see the front page and items, but clicking on settings or items/tags will require you to log in.
- You can set a password and turn off the public front page. When switching to this user you will immediately be required to login with the password you set.
The other option on the user page is to create an auto-login url. If you turn this on then a url is generated that allows anyone hitting it to login as that user. If you need to change the url, go to the user, turn the option off, save, go back in and turn it on and a new url will be generated when you click save. You can find the generated url on the list page.
The video below is an old version of the multi user capability before it was finished, but will give you an idea how it works.
All assets free range and locally sourced
With v2.0.0 all assets are sourced locally, so no reliance on an internet connection for the app to work properly. In addition we were including the Raleway google font but not actually using it, so this has now been removed.
There are now links in the settings page to the various support resources, namely the Discord server, the github page and this blog.
Basic auth login (Experimental)
If you have basic auth setup in front of Heimdall (Reverse proxy?) as long as those credentials are passed on as either a standard basic auth
HTTP_AUTHORIZATION token or as
PHP_AUTH_PW you will be automatically logged in with those credentials (if a valid user).
In nginx you can do this with:
fastcgi_param PHP_AUTH_USER $remote_user; fastcgi_param PHP_AUTH_PW $http_authorization;
In Apache something like:
SetEnvIfNoCase Authorization "Basic ([a-z0-9=]+)" REMOTE_AUTHORIZATION=$
Multi arch docker
The quickest way to get started with the app is to use the docker. The official docker is now also multiarch, so it doesn’t matter if you are installing on x86-64, armhf or arm64 the same docker image works on them all.
As always support is available in the discord channel https://discord.gg/CCjHKn4
Installing Docker and Heimdall Application Dashboard on Ubuntu
https://github.com/linuxserver/Heimdall Version 2.0.0 brings two of the most...