Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello Team,
We had setup our SAML authentication with Forgerock OpenAM with help from Professional Services team couple of years ago. Qlikview server are hosted on Windows OS and Web server is using IIS. As we were running the product outdate, we performed the upgrade of the Qlikview servers from 12.6 SR1 to 12.80.
After the upgrade, we were unable to login to the Access point. In our login Module in IIS, we updated our web.config for the login from
<add key="FrontendQVTryPath" value="/Login/SamlAuthn" />
TO
<add key="FrontendQVTryPath" value="https://ourqlikviewaccesspointurl/Login/SamlAuthn" />
After that we performed IISreset and also did a server reboot and the access point loaded fine for almost two weeks. Now suddenly it stopped working again. Checked with our IDP team and they confirmed there is no issues at their end, there was no patching on the servers by our patching team.
Came across this post in community, however still unable to resolve the issue.
https://community.qlik.com/t5/Official-Support-Articles/QlikView-and-SAML-with-OneLogin/ta-p/1711628
Anyone faced any similar issue and if any suggestions on what else can be checked?
I think the upgrade to 12.8 was successful because it runs afterwards for two weeks. If it's now failing the reasons are very likely any current changes from various stuff, like OS, security tools/measurements, network-stuff ...
Detecting the real cause could be quite hard. If it's within a VM environment with quite current snapshots you may go n days/hours back and see if it's working or not and if it worked how a successful login looked per trace or more specialized tools like WireShark - in each case it should give valuable hints.
Beside this a look within the various OS/QV logs may also produce some insights.
any recent OS patches? as @marcus_sommer mentioned perhaps revert to a snapshot.