Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
We have a global project where we need to fetch data from google sheets (for different regions) and create a dashboard. Since each region has a different data protection law, we are not allowed to use the same ID to read the data (using Qlik Web Connector).
Just wanted to understand if there is a way to configure the Web connector in such a way that we can use different IDs to read data from different regions.
Regards,
Bhaskar
I think you have two options:
- Select the 'Embed token in request URL' when you run the table, this should then generate a load script specific to that user.
- If you are using the windows forms auth for the connectors, you could create a user per GMail account and use each specific user to generate the load script (and use the default option of 'Use token from user settings' under the authentication token.
Hi - When you say IDs - I assume you are referring to Google login credentials (email + password)?
And is this with the standalone version of Qlik Web Connectors on Windows?
Yes, I am referring to gmail ID, with which the files are shared. We are using standard Qlik Web Connectors for Windows.
Regards,
Bhaskar
I think you have two options:
- Select the 'Embed token in request URL' when you run the table, this should then generate a load script specific to that user.
- If you are using the windows forms auth for the connectors, you could create a user per GMail account and use each specific user to generate the load script (and use the default option of 'Use token from user settings' under the authentication token.
Currently I have just one connection for fetching data
URL: 'http://localhost:5555/'
Name: QlikGoogleConnection
And the script looks like this:
let vQwcConnectionName = 'lib://QlikGoogleConnection';
TBL:
LOAD
*
FROM [$(vQwcConnectionName)]
(URL IS [http://localhost:5555/data?connectorID=GoogleDriveConnector&table=GetWorksheet&encrypted_refresh_token=sta_gen_1%3a########&worksheetKey=1ogwgk##########&appID=], qvx);
So every developer I have given access to this connection is able to fetch data from any region/country. Which we want to avoid. Also, we can't afford to create different connection for every table the developer is fetching - as there are hundreds of tables.
We want the developers to be able to fetch data only for the country that they are supposed to be developing for.
For example:
Developer1 - works for APAC, has a access to a connection1 (configured with email_ID1) that can fetch data only for APAC
Developer2 - works for EMEA, has a access to a connection2 (configured with email_ID2) that can fetch data only for EMEA
Developer3 - works for Americas, has a access to a connection3 (configured with email_ID3) that can fetch data only for Americas
Is it possible to configure something like this?
Regards,
Bhaskar
I think it is yes - using my option 1 above. It looks like you are already using the 'Embed token in request URL' option so as long as you have authenticated with the correct user when you generate the load script in the QWC web UI, the encrypted_refresh_token in that script will be specific to email_ID1, email_ID2 etc.
Thanks Chris. It's working the way I was expecting.
Thanks again,
Bhaskar