topic Re: Move from jwt-proxy to M2M Impersonation workflow in Integration, Extension & APIs

Move from jwt-proxy to M2M Impersonation workflow

AkshayBheda — Tue, 03 Sep 2024 20:01:08 GMT

Hi,

Currently we are using JWT Proxy workflow with section access. We use qlik mashup api's to load the qlik app.

We would like to continue to do so, but the current issue we are facing is socket's disconnection while relaying the requests. We would like to remove our backend so that it can directly connect to qlik.

Is this something possible with M2M? I could not find any examples for M2M with mashup api's. We cannot use qlik embed since we would need to we-write the application itself.

@Jeffrey_Goldberg Could you provide any input on this? as you suggested the initial approach for proxy when there M2M impersonation was not available?

Thanks,

Akshay

Re: Move from jwt-proxy to M2M Impersonation workflow

alex_colombo — Thu, 05 Sep 2024 12:29:58 GMT

Hey @AkshayBheda you cannot use M2M direcly from a web app (client). You have to create a backend service which make the M2M request on behalf of user, then pass the OAuth token to the webapp for using it and impersonate the user in the browser session. Here an example of this process.

Re: Move from jwt-proxy to M2M Impersonation workflow

AkshayBheda — Mon, 09 Sep 2024 12:15:00 GMT

@alex_colombo we do have the .Net backend and we have angular frontend. We use qlik mashup api's. I could see how its used with qlik embed, but i couldn't see any thing with qlik mashup and M2M Oauth with user impersonation

Re: Move from jwt-proxy to M2M Impersonation workflow

Jeffrey_Goldberg — Mon, 09 Sep 2024 12:18:22 GMT

M2M OAuth impersonation is available with qlik-embed. It is not available with existing capability API. We will have some tutorials and examples for migrating from capability API to qlik-embed showing up on https://qlik.dev soon.

Re: Move from jwt-proxy to M2M Impersonation workflow

AkshayBheda — Mon, 09 Sep 2024 14:45:00 GMT

Thanks, that would help. We are interested to move to qlik embed but the thing limits us is selection of individual elements which is possible in capability API.

Re: Move from jwt-proxy to M2M Impersonation workflow

AkshayBheda — Wed, 11 Dec 2024 09:54:33 GMT

Hey, just wanted to check if selecting single elements is not possible with qlik embed, and also with M2M impersonation, can we also create users if they don't exist?

Re: Move from jwt-proxy to M2M Impersonation workflow

alex_colombo — Thu, 12 Dec 2024 16:14:45 GMT

@AkshayBheda what do you mean by selecting single elements? Embedding single visualization using qlik-embed? If so, yes it is possible.

Re: Move from jwt-proxy to M2M Impersonation workflow

AkshayBheda — Thu, 30 Jan 2025 18:27:59 GMT

@alex_colombo This will work if the user has already a account, but when user log's in for the first time this workflow won't create the user.

I believe @Jeffrey_Goldberg knows the workflow I am talking about

Re: Move from jwt-proxy to M2M Impersonation workflow

alex_colombo — Fri, 31 Jan 2025 15:09:50 GMT

That's correct, M2M impersonation will not create users. For creating users you can use users APIs along with Groups API (groups are released yesterday and creating them manually will not support section access) or JWT authentication. I recommend to use JWT at the moment, waiting for full support from Groups API.