Hello guys,
In Qliksense cloud app; signing in user takes you to the Idp page (login.qlik.com/login?state=tettesttest) where you can provide the credentials and it redirects to the Qliksense cloud instance (https://mycompany.au.qlikcloud.com).
I am looking to replicate the similar scenario of ticket authentication as done in Qliksense/Qlikview enterprise with Qliksense cloud SaaS.
1- custom authenticate user from the database.
2- generate a token (which can be embedded in the url)
3- redirect user to the Qliksense cloud instance page (with the embedded token).
I have seen different help pages/tutorials and found that we can generate a token to do the Qlik Saas API calls
https://qlik.dev/tutorials/build-a-simple-c-oauth-client-to-access-qlik-sense-saas
https://qlik.dev/tutorials/create-signed-tokens-for-jwt-authorization/#example-of-jwt-signing-code
but the question arises is that what be done with this token? Either this token can be embedded in the URL to bypass the Idp page or can be used to do other API calls which is not my intention.
I am just looking to bypass this Idp page (by embedding the token/ticket). I seen one link similar to what I am looking to achieve.
https://help.qlik.com/en-US/blendr/Content/documentation/sso-integration-for-saas-partners.htm
"
Example SSO link using a JWT:
https://saaspartner.admin.[ca|us|au].blendr.io/sso?jwt=xxx
"
In this link they are just embedding the jwt in the url and it seems like bypassing the authentication Idp page.
Kindly let me know is it the right approach to the requirement or do I need to take some other approach.
Kind regards,
Raza
