Open Chricky opened 6 years ago
I have the same problem, it looks like the client.pfx certificate used by the api is always required to be the one generated by Qlik, so even if you replace the server.pfx in the login module with a third party signed certificate and use this to request the ticket, the error will persist as the client.pfx will always be self-signed.
Not sure if there is a way around this one.
Cheers, Ryan.
Hello,
is there a way to make the custom login page work on https. Right now, when I set the ports to default https port and do change the part for creating a https-page in the .js file, I still do receive an https-error and chrome (or any other browser) tells me the page is not safe/running as https.
Regards Chris