Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
My company is trying to achieve API Session Solution with a Qlik Sense 2.1.1 embedded solution.
Under this Authentication Solutions article:
I see 5 authentication solutions:
But under QMC => Virtual Proxies => Authentication => "Authentication method" I see four choices:
I expected to see a choice named "Session" or "API Session" or "Session Cookie". I want the cookie we are writing from our Identity Provider named "X-Qlik-Session-Custom" to be read just as the Session Solution article describes.
Q) How do we properly configure via QMC to achieve the Session Solution?
thank you very much,
Michael
Please see the following videos:
Overview: https://drive.google.com/file/d/0BxBEVQthCb29T1NIUUxmTnZGWEk/view?usp=sharing
Session api IIS config: https://drive.google.com/file/d/0BxBEVQthCb29ek52R2pCZ3ZOX00/view?usp=sharing
Session api: https://drive.google.com/file/d/0BxBEVQthCb29b3l1ME1SQXpkZkU/view?usp=sharing
These may help you.
jg
Please see the following videos:
Overview: https://drive.google.com/file/d/0BxBEVQthCb29T1NIUUxmTnZGWEk/view?usp=sharing
Session api IIS config: https://drive.google.com/file/d/0BxBEVQthCb29ek52R2pCZ3ZOX00/view?usp=sharing
Session api: https://drive.google.com/file/d/0BxBEVQthCb29b3l1ME1SQXpkZkU/view?usp=sharing
These may help you.
jg
Yes, thank you Jeffrey.
The last two videos were helpful to help us figure out our issues with the Session Solution. I wish those videos were available through the help.qlik.com site.
thank you,
Michael
Hi Jeff,
I know I am asking this after long time but I an trying to do the same thing in my java web application.
I have already authenticated user in my portal using a custom form, added the same session in qlik using session api and set the response cookie.
I assume QPS should look at that session cookie and match , if any session id present with the same value , it should allow us to get the content. In case user directly visit qlik hub then it make sense to redirect the user back to my custom form ( authentication redirect URI should be used).
When I am trying to access hub after authenticating the user in both portal and qlik, Qlik redirects it back to my portal after appending proxyRestUri and targetId as query parameter in redirect URI.
Since my user is already authenticated at my portal, the user stays on my portal page.
I am not sure what is wrong, I assume qlik shouldn't redirected the user back to my portal as session of user is already exists.
Thanks
-Vishal
Vishal,
Sounds like if you are getting redirected back to the portal again and not surfacing Qlik content you want to review the virtual proxy path in your calls to Qlik Server. You may be setting up the authentication for the virtual proxy, but you need to make sure your calls to resources go through the same virtual proxy path or Qlik Sense is going to redirect you for a new cookie.
It reads like you have all the other items I'd reviewed checked.
jg
Thanks a lot Jeff for your response.
I debugged it a little more and found that the cookie is not passed to qlik when I request for qlik resources ( through mash up).
My qlik and portal resides on different sub domain.( might be in separate domain altogether).
In that case I won't be able to set cookie. So can we say this won't work in case of cross domains ?
Now redirect module URI is set to my portal login page and when unauthenticated user try to access hub they are redirect back to my portal by appending proxyRestUri in the URL. I need to redirect the user back to hub once authenticated.Do I need to handle this in my portal login module ?
The proxyRestUri is actually not a back url where user should be redirected back. In my case its coming as
proxyRestUri=https://MACHINE_HOST_NAME:4243/qps/eztest/&targetId=6bbc141d-5f36-41f1-a7e0-2eae60aa593f
Instead of domain name its adding machine host name and also the actual hub is missing.
Thanks
-Vishal
Hi Jeffrey,
I tried accessing the links but unable to open the links, are those still active?
Thanks & Regards,
Kumar.