topic Natural Language API and Section Access (SaaS) in Integration, Extension & APIs

Natural Language API and Section Access (SaaS)

BogdanF — Tue, 25 Jun 2024 13:01:14 GMT

Hi, all. I want to use this API: https://qlik.dev/apis/rest/questions/.

But my apps have the "section access" and different users should get different answers.

How to do it?

Re: Natural Language API and Section Access (SaaS)

alex_colombo — Fri, 28 Jun 2024 13:52:54 GMT

Hi @BogdanF , you have to authenticate using the correct user for leveraging section access rules for that particolar user. If you use a specific user, then section access will be applied and you will have answers with data filtered by section access.

Re: Natural Language API and Section Access (SaaS)

BogdanF — Mon, 08 Jul 2024 11:38:19 GMT

Hello Alex. Thank you for your response.
According to the documentation, I use Api-key for authenticate "Authorization: Bearer <API-key>".
How can I authenticate a user? Can I use JWT? Do you have an example?

Re: Natural Language API and Section Access (SaaS)

alex_colombo — Mon, 08 Jul 2024 15:45:13 GMT

If you will use API-Key, you cannot authenticate with your users and section access will not be applied.

You have to authenticate using OAuth with impersonation, or JWT. Here some info.

Re: Natural Language API and Section Access (SaaS)

BogdanF — Tue, 09 Jul 2024 09:16:44 GMT

I know JWT. I use it to authenticate users in the Qlik Cloud.
But are you sure I can use it in "Natural Language API" (https://qlik.dev/apis/rest/questions/)?
"Authorization: Bearer <JWT-Token>"?
Here I found it:
"
The Natural Language API does not check section access controls in the app's load script. If an audit administrator has the Developer role and can open apps (as provided through the space permissions), they can view the app usage metrics.
"?

Re: Natural Language API and Section Access (SaaS)

alex_colombo — Tue, 09 Jul 2024 10:35:58 GMT

Yes, you should be able to use it. Try to generate a JWT token and then attach it to the header of your REST API call. You should be able to authenticate.

Re: Natural Language API and Section Access (SaaS)

BogdanF — Tue, 09 Jul 2024 13:03:45 GMT

It looks like it's not working.
I'm testing using curl.
When I used this: curl https://MyTenant.eu.qlikcloud.com/api/v1/questions/actions/ask -X POST -H "Authorization: Bearer <API-KEY>"....
I received the correct JSON response.

But when I used this: curl https://MyTenant.eu.qlikcloud.com/api/v1/questions/actions/ask -X POST -H "Authorization: Bearer <JWT-Token>"....
I received:
"
<html>
<head><title>401 Authorization Required</title></head>
<body>
<center><h1>401 Authorization Required</h1></center>
<hr><center>nginx</center>
</body>
</html>
"
The JWT token is probably correct because it works outside the API.
What else can I check? Is there an example of using JWT with the Qlik API somewhere?

Re: Natural Language API and Section Access (SaaS)

BogdanF — Fri, 19 Jul 2024 12:39:38 GMT

Hello Alex. Do you have any advice?

Re: Natural Language API and Section Access (SaaS)

TcnCunha_M — Fri, 19 Jul 2024 12:42:12 GMT

Have you try this?

ChatGPT in Qlik Sense

Re: Natural Language API and Section Access (SaaS)

BogdanF — Fri, 19 Jul 2024 12:50:21 GMT

This is not an Qlik Natural Language API.
I want to use Natural Language API.

Re: Natural Language API and Section Access (SaaS)

alex_colombo — Wed, 24 Jul 2024 10:41:36 GMT

Did you initialize JWT auth flow using /login/jwt-session end point?

When you have generated your JWT token you have to:

Initialize login flow posting a request to /login/jwt-session
Get a Qlik CSRF token attaching JWT token to request headers. Note that Qlik CSRF token will be added to response headers.
Call /question end point attaching Qlik CSRF token and JWT token to headers.

Everything is explained here.