Using Keytiles TileView on unattended machines
Here are some tips how to make this done!
Content of this page
Due to security considerations Keytiles requires re-login again and again periodically (currently it is one week). For users it is not a big deal. However it is definitely a pain in the ass in use cases when you are projecting out Keytiles screens using an unattended machine. You can solve this easily. but
You will sacrifice the above security barrier by doing this! So follow the below steps carefully to at least minimize the risk!
Follow these steps to get this done:
- Create a "technical user" account on the System UI
Just simply register one user. This account should be used only in this use case and you should not share or publish the login info of this account!
- Grant "view" permission to this user
Never grant "admin" permission just "view"!
- Now log in with this user account
using your browser into the System UI
- Open the "developer tools" panel of your web browser!
Normally this happens with pressing F12 (Chrome and Edge)
- Find the cookie named "_kt_authToken" and copy its value to the clipboard!
- Add this value to the URL of the TileView!
When you open the TileView you will get a URL similar to this. Just add the "authToken" query parameter (see highlighted below) with the value on your clipboard!
- Test it! The URL should work without asking for any login
The URL we just created grants permission to get into the view for everyone who knows it for indefinite time! Make sure this URL is not indexed accidentally by search engines so do not publish this on any public web pages!
If you feel the URL might be exposed then change password of your technical user and re-capture the new auth token!
Due to the unsecure nature (see above) these request will generate a Warning in a standard browser Alert (to ensure you can not easily skip it) for you. Which might cause you issues in a fully unattended setup. So to get rid of that warning (risks understood and acknowledged at this point right?!) you can add a skipAuthTokenWarning=true parameter to the URL.
OK this is easy! :-)
Please note as you navigate to different screens on the TileView the URL changes every time. To put it this way: the URL points to the screen and also encoding all the settings you made. We can use this for our own advantage!
Here is what you can do:
- Go to the screen you want to beam out! Adjust the settings if needed!
- Capture the URL or just leave this on a browser tab
- Open a new browser tab and go to a different screen - do the same
- Repeat 2,3 until you have everything opened the way you need
- Now comes the trick! Find a browser plugin which can either
- rotate between opened browser tabs, or
- rotate between a list of URLs
And voila, you are done!
You will find lots of browser plugins for the above - just pick your favourite!
In one of the future versions of the UI we will provide a feature for this making all of this easier. So consider the above workaround temporary!