search

qlik-demo-team / qdt-components

React Components to be used with Angular 10, React 16 and Vue 2. Connects with the Capability API and Engine API.
MIT License
92 stars 50 forks source link

Windows authentication prompt shown when Ticket authentication is in place for a virtual proxy #37

Closed praveena-m closed 4 years ago

praveena-m commented 6 years ago

I have followed the guide for using qdtcomponent for React mashup app, for some reason, I keep getting windows authentication prompt. I have a ticket generated using the API. I have successfully authenticated to Qlik server by requesting image and received qlik session cookie. I even tried passing ticket to connections.useUniqueSessionID with no luck.

Any help on this issue would be greatly appreciated!

network

miranda-elliott commented 6 years ago

I'm having the same issue. Have you made any progress on resolving this?

yianni-ververis commented 5 years ago

In order to do ticketing, we need to modify headers which cannot be done via a browser, only with server side scripting.

miranda-elliott commented 5 years ago

@yianni-ververis If this is the case, is it possible to use qdt-components to load objects from a Qlik Sense app that requires authentication? Don't all of Qlik's methods of authentication require headers?

fkabinoff commented 5 years ago

That's really odd though. If you have a valid cookie, it should not prompt for authentication, and it's not really even anything that qdt-components is doing specifically, if you notice it's the request for the capabiliy api css resources that triggers it...hmm...any more info on this? Was this ever resolved?

dreadeyedave commented 5 years ago

I was getting the same issue, however I found it was because I was requesting my session from server ip (10.0.0.1), and requesting my objects from dns web address (example.com). Hope this helps

fkabinoff commented 4 years ago

im closing this. theres nothing in any of these comments that suggests this is a problem with qdt-components. when i look at the first image i can see that when the require.js file is requested its returning a 302 which is what it does when a user doesn't have a valid session cookie for that virtual proxy, and this has nothing to do with qdt-components itself. find me on qlik branch slack if you're having general authentication troubles with qlik and mashups, will try to help there.