Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello everyone,
while playing with the QDC demo environment I noticed that the connection to Qlik Sense is set up with QSE JWT token. My question is: can we connect QDC to a QSE environment with old licence type (key/control number) or is new license type a requirement?
Thanks.
Juraj
Hi,
Here are the instructions to setup JWT authentication on Qlik Sense : https://support.qlik.com/articles/000034966
It has nothing to do with the QSE license type.
Best regards,
Thiebaud
Its has a problem or does not seem a good instuctions on material to do this.
If you check the jwt token generate on QDC demo release by qlik i share bellow
#0{gtErmgzvXnDZpq7ooq25jzQl1HqNqjHrMIvbbv3uaef2Jftdn92rap9wLQbPLd27z54E8yuERvKC8jXHsgHeP6KeOtDg5lwekwHZr87Oqz9je8iLvwhUSHKW4VuJIWewn8o1QWXv1Y0ZwVR+Ks1NQlTKCN/yTu/Jac9MO9a/SVSxVZzsmE/WuwaFiBC1k9eW5ubH2xFIieGqrEENWxXjl8Kk2LD8En2xsw7mIqQ/eroqM3V4k8wCDJrswfauLMm9nS1K5crdpa4MfCs3zvyEHDJxetdNLB5Lz+SLUdItaFfHuCJ/HDgFABJckc3K31nYRjeEG9B/hh9XXVLZWe++h3e5QTroMDB5f5unMq5t7e6+q3u00VXje/82Nz2A5/uwC0P7Z92c9TL9IVoMqZZdBTjcCsFeW9geoG40MVhI757TVXeTGHyjL3fSGL/kxZ4VTf9i3FRirQZVo5lYtuYWBjYKYwgb2r5Rq0+GjC6tgmHU29uhzrwa0hdNNXJN7T8CJSjxpPsxj7aEEyYuWh1ookZRvqsO0rGq9PG2MTH6HMGIEatbh5fcPyNZEl+8AwSO2bjoB1Y5CJnqz3jpLEAMcA==}
The format is complete different if compare the jwt.io (according the documentation).
If you use this
Connection name: sense1.qdc-demo.com
Host: sense1.qdc-demo.com
Proxy: qdc
JSON Web Token: use above
Default QVD Mount Point: use any directory
QDC Base Directory: /usr/local/qdc/data
Working good, but if you try with your qlik sense does not work. JWt.io generates different "layout" in your token.
its to bad relase documentation makes we has to much problems.
Hi,
Here are the instructions to setup JWT authentication on Qlik Sense : https://support.qlik.com/articles/000034966
It has nothing to do with the QSE license type.
Best regards,
Thiebaud
Thanks for feedback Thiebaud
Well, i will be shared bellow the prints about my config.
I used the check-proxy.js provide in Qlik Pack Installation.
if you see i believe the jwt auth works correct. i shared 2 prints about the return of check-proxy.js. In one image the brackets is empty (according the documentation). In this case i use the Qlik Sense November 2018. If you check the next i receive data (not empty brackets), because in this case we has a Qlik Sense June 2019. In same cases i undertand the auth is corrrect.
After this test i will be use the jwt token in Data Catalyst but does not work. If you check the demo Data Catalyst provide in accreditation the token has another format (probably encripted).
I used the utility and the token i believe now is the same format in the QDC demo but does not work either.
I shared a zip file with the prints (because the forum limit a number of attachments).
The problem solved when using the valid certificate (self signature does not work).
I use for test https://certbot.eff.org/
Hi,
Thank you for your feedback.
When you say "I used the utility and the token i believe now is the same format in the QDC demo", which tool are you talking about ? How have you converted the jwt token in the encrypted state ?
Thanks
In installation pack we has a file call podium_localhadoop.jar.
Use this command
java -cp podium_localhadoop.jar:. com.nvs.core.utils.PodiumEncrUtil
Use option number 1 and put the jwt token.
I share the screen about this.
Thank you for your answer.
Sadly I still have the "Could not fetch data from QS due to issues with connection" error when using an encrypted JWT token and a valid cert...
I will try to figure this out.
they need a valid certificate. Its possible to use a certbot https://certbot.eff.org/lets-encrypt/centosrhel7-apache.html.
Create a cert for apache. This app generate 2 files, cert e key (pem file).
Use a xca (X certificate and Key Management) https://sourceforge.net/projects/xca/
This app made a cert for windows (pk12 cert wtih private key) (using the files generate by certbot).
After install in windows using the thumbpring in proxy server and retry.