search

Informatiqal / qlik-rest-api

Interact with multiple Qlik Sense REST APIs from a single package
MIT License
7 stars 0 forks source link

Documentation Request - Passing Additional Auth Attributes #5

Closed aburnsy closed 2 years ago

aburnsy commented 3 years ago

Hi Stefan,

I'm unsure if this is an issue itself or its just a matter of documentation. When authenticating I need to pass over additional attributes that will be used in Security Rules + Section Access.

Using enigma I think you pass something like this: Attributes: [{ Group: '1234' }, { Group: '5678' }, { CLIENT: 'COCA COLA' }]

Is this available today? I've tried a few different variations and can't seem to get it to work. It might just be how I am doing it though.

Thanks again, Andy

countnazgul commented 3 years ago

Hmmm not sure i can find anything in Qlik's documentation about it. Any chance these attributes are to be used with JWT authentication?

aburnsy commented 3 years ago

Not necessarily. One example below:

https://help.qlik.com/en-US/sense-developer/April2020/Subsystems/ProxyServiceAPI/Content/Sense_ProxyServiceAPI/ProxyServiceAPI-ProxyServiceAPI-Authentication-Ticket-Add.htm

countnazgul commented 3 years ago

Sorry Andy, i though i've answered to this one but apparently i haven't submitted my comment

The attributes, you've mentioned, make sense in the Proxy context. And they can be passed in the body as usual. In Repository context (for example) these attributes can't be passed (or even if they're passed the repo api will most likely ignore them)

In Repo's context the attributes will be based on the authenticated user. So if using JWT as authentication these attributes will be part of the JWT itself

Let me know if this makes sense or i've misunderstand the question