Yes I am using SP initiated SSO using SAML. I have embedded qlik sense sheet using an iframe in my external portal. My portal and qlik both acts as SP and participate in SSO. On the landing page of portal I have redirected user to qlik and then back to portal so that all required cookies are set for portal and qlik sense.
I see this issue even when I directly go to Single through my virtual proxy which usage SAML.
UPDATE : This happens even if I use windows authentication, If require js and single js gets loaded within 10 to 12 sec , it works fine but in the errornous situation, single js take almost 20 sec to load.
Yes exactly this is the flow and this is what is happening.
Also as I said I see this issue in default proxy as well when using windows authentication. If I go to /single and refresh browser there are chances that it works sometime. In the log I see the same thing I mentioned in the original post.
I tried this as well and the problem still persist. Could it be a case of snatching session ? It is possible that multiple users are sharing the user id and when someone refresh the browser it tries to create a login with the new client and then tries to fetch JS which takes a lot of time and hence gives load timeout.
The logs says "Authentication failed because the remote party has closed the transport stream".