Open ludberg opened 6 years ago
Hi Anders, requirejs has been updated in Nov release, that's the reason of the your stack. I've updated it, please let me know if it works. Tx !
I got past this problem but now I get the following problem
The Alert is on line 174 in spotify-session-app.js.
I guess I have problems with my Virtual Proxy. Can you provide a screenshot of ALL the settings in a working Virtual Proxy?
Edit: I'm now trying on the same server where I have the Sense server installed
Should Session module base URI be http://localhost:3002/**main or http://localhost:3002/session**
Should I use Authentication method: Ticket? Should I allow anon loggins?
It doesn't matter how I configure my Virtual Proxy, it gives me a 500 Error when trying to access https://localhost/ano/hub
Any ideas?
here's the high level flows, yes the session url must be "session". You can first try with desktop, it will will help to spot potential problems and understand the flows. I admit the doc is far for being perfect, apologize :-( I'll post the vp settings asap but need to setup a server first. I''ll give then you answers for the other questions (auth, anonymous).
I did get it working on desktop about a year ago but not I want it running on a server so our sales people can access it.
It looks like the session-url is not working properly. As soon as I add http://localhost:3002/session to the Integration-park of the Virtual Proxy, I get a 500 Internal Server error.
Please set it up yourself and post the correct configuration.
Hi Anders, here's my vp, the session module was wrong:
Here's my settings and this doesn't work
The error I get in Chrome
My settings in your script
My virtual proxy settings
Does your proxy allow "http" ?
Yes it does
On Feb 21, 2018 16:58, "Anthony Alteirac" notifications@github.com wrote:
Does your proxy allow "http" ?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/aalteirac/spotifySessionApp/issues/5#issuecomment-367373494, or mute the thread https://github.com/notifications/unsubscribe-auth/ADD0hg-LdL7LV86CUIq7nlgPK_bkZvD9ks5tXDzrgaJpZM4R_qV4 .
oki, that's gonna be difficult to debug. I'll setup another server with Nov release on my side and will try to reproduce. Stay in touch
I'm actually on 2018 Feb and it doesn't work either :(
Thank you for you effort to solve this! It will be very helpful for me
Hi Anders,
quick recap: I have Nov release installed and it works fine for me. The error you have shows the /session endpoint of the module is not called. Please double check if the config is correct "X-sess" in vp and config. (looks fine in the screen shot). Check the cookie is created on localhost:3002, in chrome debugger/tab application
just in case... does your VP linked to the proxy ? and vp tight to central engine ?
Also, be sure the url in the front config is the same used to access the mashup site:
This is driving me mad.
I can't get past this error!
It doesn't matter if I try
localhost/ano/resources/js/qlik.js or 192.168.1.143/ano/resources/js/qlik.js or ex188/ano/resources/js/qlik.js
I can access the qlik.js file if and only if I remove "http://localhost:3002/main" from the Session Module Base URI.
Is there any other option somewhere in the QMC I need to change or apply? The Virtual Proxy is Linked to my Proxy Service but not set as default.
If I remove http://localhost:3002/main from the Virtual Proxy I get the following error
ERROR on createSessionApp Error: Not connected at RPC.send (C:\Users\anders.uddenberg\Desktop\spotifySessionApp2\node_modules\enigma.js\dist\enigma.js:3119:37) at Session.send (C:\Users\anders.uddenberg\Desktop\spotifySessionApp2\node_modules\enigma.js\dist\enigma.js:1569:32) at Object.fn [as getActiveDoc] (C:\Users\anders.uddenberg\Desktop\spotifySessionApp2\node_modules\enigma.js\dist\enigma.js:2776:32) at qix.global.createSessionApp.then (C:\Users\anders.uddenberg\Desktop\spotifySessionApp2\engine.js:178:25) at <anonymous> at process._tickCallback (internal/process/next_tick.js:188:7) Error: Not connected at RPC.send (C:\Users\anders.uddenberg\Desktop\spotifySessionApp2\node_modules\enigma.js\dist\enigma.js:3119:37) at Session.send (C:\Users\anders.uddenberg\Desktop\spotifySessionApp2\node_modules\enigma.js\dist\enigma.js:1569:32) at Object.fn [as getActiveDoc] (C:\Users\anders.uddenberg\Desktop\spotifySessionApp2\node_modules\enigma.js\dist\enigma.js:2776:32) at qix.global.createSessionApp.then (C:\Users\anders.uddenberg\Desktop\spotifySessionApp2\engine.js:178:25) at <anonymous> at process._tickCallback (internal/process/next_tick.js:188:7)
Could it be a certificate issue?
What's the emptyAppID and directory below? Should I do something in the QMC with them?
emptyAppID:"82df6f83-a835-4587-ab8f-76c20155dbfc", hostname:'localhost', cookieName: 'X-sess', directory:'CUSTOM', prefix:'/ano/',
I found the solution. I needed a Access Rule and allocate a token to the user.
Now I'm stuck on these erors:
446 11.34.2.0 20180224T122759.761+0100 WARN ex188 793dfac1-f4ab-4440-a135-4664d5a294c8 Command=Open connection;Result=-2146233079;ResultText=Error: Fjärrservern returnerade ett fel: (404) Kunde inte hittas. 0 0 0 INTERNAL sa_proxy 0 Not available Proxy Not available Not available Open connection -2146233079 Web exception: Protocol error: Response stream exists. Remote endpoint 'http://localhost:3002/main' 793dfac1-f4ab-4440-a135-4664d5a294c8
Here's a quick update. Apparently there is a hard-coded ClientId (spotify) in line 84 of public/login.html. This is your client id :)
Once I changed this to my Spotify Client id I get this error:
Request URL:http://ex188:4248/windows_authentication/?targetId=d648cbad-bb96-4002-be7e-2623655933c2
Request Method:GET
Status Code:400 Bad request: Couldn't find virtual proxy derived from targetId d648cbad-bb96-4002-be7e-2623655933c2
Remote Address:192.168.100.141:4248
Hi, A lot of different things :-) If you remove the session module you won't be authenticated, or wrongly authenticated for my logic. The session endpoint is not for direct access (requires a cookie otherwise raises 500) The empty app guid doesn't need to be changed, no app or QMC settings needed. My client ID is indeed in the login ;-) forgot to remove but it's not secret, no worries. I think your problem comes from the session module and cookie creation. You're doing a lot of tests but I'm missing the context when some errors happen, really hard to try to reproduce on my side. The only thing I can propose to help is a live debugging session over webex, otherwise I'm afraid it will be hard. Please ping me by email and I will arrange.
Thanks
I followed the readme but got a lot of errors.
I'm running Qlik Sense Desktop November 2017 Patch 2
What might be the problem?