Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
AG-gugelbisolutions
Creator II
Creator II

Session Authentication example

Hi there, I'm struggling to make this example to work.

As mentioned in the comments, I downloaded the session module template from GitHub and followed the rules to run it with Node JS over port 8190 with client certificates.

Of course, I made some changes:

  • create a new virtual proxy
    • with a unique name and prefix ("mashup")
    • Ticket/Form authentication
    • with a unique session cookie header name (X-Qlik-Session-mashup)
    • with the following white list: localhost, <public domain>, <server-name>
    • with http://localhost:8190 as session module base URI
  • within SessionAPITestModule.js
    • var RESTURI = "https://<public domain>:4243/qps"
    • fixed certificates name and passphrase
    • added "mashup" prefix where needed (/redirect endpoint)
    • used X-Qlik-Session-mashup instead of the original cookie name
  • within SelectUser.htm
    • modified the userDirectory parameter to our user directory (server name)
    • reduced the number of lines and users to three to match users of ours

With this setup, running on localhost, I'm able to create a new session and set the cookie, but when I try to get access to Qlik Sense (through the new VP), the system replies with an internal error. Proxy logs say this: 

The underlying connection was closed: The connection was closed unexpectedly

Web exception when contacting service uri http://localhost:8190/

Is there, maybe, a better guide to follow?

Labels (2)
0 Replies