Ever wanted to brand or customize the default Qlik Sense Login page? The functionality exists, and it's really as simple as just designing your HTML page and 'POSTing' it into your environment.
We've all seen the standard Qlik Sense Login page, this article is all about customizing this page.
When getting started, I would strongly recommend setting up a new virtual proxy with 'Forms' so you don't impact any users that are using auto-login Windows auth.
The virtual proxy settings would look something like this:
Now once this is done, a good starting point is to download the default login page. You can open up your web developer tool of choice, goto the login page, and download the html response from the GET http://<server>/customlogin/internal_forms_authentication request. It should be roughly a 273 line .html file.
Once you have this file, you can more or less customize it as much as you'd like. Image files can be inlined as you'll see in the qlik default file, or can be referenced as long as they are publicly accessible. The only thing that NEEDS to exist are the input boxes with appropriate classes and attributes, and the 'Log In' button.
After building out your custom html page and it looks great, it needs to be converted to Base64. There are online tools to do this, openssl also has this functionality.
Once you HAVE your Base64 encoded HTML file, then you will want to PUT it into your sense environment.
First, do a GET request on /qrs/proxyservice and find the ID of the proxy service you want this login page to be shown for.
You will then do a GET request on /qrs/proxyservice/<id> and copy the body of that response. Below is an example of that response.
You can then take your base64 encoded HTML file, paste that value into the 'formAuthenticationPageTemplate' field. Once you have an updated body, you can use the PUT verb (with an updated modifiedDate) to PUT this body back into the repository. Once this is done, you should be able to goto your virtual proxy and you should see your new login page (very Qlik branded in this example):
If your login page does NOT work, you can simply do a GET call on your proxy service, and set formAuthenticationPageTemplate back to an empty string:
Once this is done, you should get reverted back to the default login screen.