Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing parameters #3

Closed
pevans87 opened this issue Jul 13, 2016 · 5 comments
Closed

Missing parameters #3

pevans87 opened this issue Jul 13, 2016 · 5 comments

Comments

@pevans87
Copy link

Hiya,

I'm sure this is a stupid question - but I'm trying to get this setup and using your starter code I'm not really having any luck - I just get a message missing parameters.

Can you give me a bit more info on how to customise this to connect to my instance of Qlik?

Thanks!

@braathen
Copy link
Owner

Hi,

You need to configure a virtual proxy in QMC, as custom authentication URL you give the URL to where your ticket code is running. Then you can just enter the url//hub or url//qmc and the user will be redirected to the ticket code. The prefix is the prefix you assign to the virtual proxy. The redirection will contain the "missing parameters", which is options.targetId and options.proxyRestUri. the idea is to simplify and minimise the code needed to get it to work, but also to provide a better "flow". It also takes all kind of hard-coding away and the same code can be used for multiple instances.

@zuruprem
Copy link

zuruprem commented Apr 1, 2017

Hi Braathen,

Thanks for qlik-auth. In the past used it very well for ticketing in Qlik Sense with node. Recently I changed default Qlik Sense port from 80 to 81 then logging into node proxy is generating following error
image

@braathen
Copy link
Owner

braathen commented Apr 4, 2017

Are you sure the port was the only thing you changed? if setup as a virtual proxy and custom authentication module with redirects the module should not care where it came from or where to redirect back as those values would be provided as parameters from Qlik Sense.

Please also check that you have set origin white list properly and that the user has a license allocated, and that there are licenses available and automatically assigned through license access rules.

@zuruprem
Copy link

zuruprem commented Apr 4, 2017

Dear braathen,

You are correct. Providing the whitelist for new virtual proxy has resolved the issue

@braathen
Copy link
Owner

braathen commented Apr 4, 2017

Great!

@braathen braathen closed this as completed Apr 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants