Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
LubosZan
Partner - Contributor II
Partner - Contributor II

Netsuite Rest Oauth 1.0

Hi,

I'm trying to connect the Netsuite with oauth 1.0 via REST connector from Qlik Sense Cloud. I can successfully load the data via postman with oauth 1.0 and "Add parameters to header" option (sample attached). I'm trying do the same in Qlik Sense with query Header parameters but with no success (error with "http protocol error 401 unauthorized: Requested resource required authentication" appeared). 


Does anybody know if this is possible and how to fix it, how to "turn on" an authorization and set the header parameters correctly?

Thank you.

 

 
Labels (1)
1 Solution

Accepted Solutions
LubosZan
Partner - Contributor II
Partner - Contributor II
Author

Header parameter must be in one row with correct separator like this: 

Header name: Authorization

Header value: OAuth realm="3866680",oauth_consumer_key="1234567890",oauth_token="1234567890",oauth_signature_method="HMAC-SHA1",oauth_timestamp="1590972088",oauth_nonce="FHMtIc",oauth_version="1.0",oauth_signature="1234567890".

But even with the right header definition I wasn't able to generate the oauth_signature in Qlik on the fly. Postman can generate this oauth signature during every GET call on it's back end (client and token secret must be defined), but Qlik rest connector cannot do that because it doesn't support the oauth authentication in REST connector (i still don't understand why). So we had to switch to OAuth 2.0 integration. With OAuth 2.0 we were able to ensure the connection between Netsuite and Qlik with Rest connector.

View solution in original post

4 Replies
LubosZan
Partner - Contributor II
Partner - Contributor II
Author

Header parameter must be in one row with correct separator like this: 

Header name: Authorization

Header value: OAuth realm="3866680",oauth_consumer_key="1234567890",oauth_token="1234567890",oauth_signature_method="HMAC-SHA1",oauth_timestamp="1590972088",oauth_nonce="FHMtIc",oauth_version="1.0",oauth_signature="1234567890".

But even with the right header definition I wasn't able to generate the oauth_signature in Qlik on the fly. Postman can generate this oauth signature during every GET call on it's back end (client and token secret must be defined), but Qlik rest connector cannot do that because it doesn't support the oauth authentication in REST connector (i still don't understand why). So we had to switch to OAuth 2.0 integration. With OAuth 2.0 we were able to ensure the connection between Netsuite and Qlik with Rest connector.

QSL_MK
Contributor II
Contributor II

I am also trying to connect NetSuite to Qlik Sense? Can you provide information how you managed to connect it?

NZFei
Partner - Specialist
Partner - Specialist

With OAuth 2.0, I still don't know where to put tokens. Can you please shed any light on it?

 

Thank you.

 

Fei

Gene_K
Partner - Contributor II
Partner - Contributor II

anyone figured this out?