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: 
Anonymous
Not applicable

Google Cloud Storage Identification failing in tBigQuery_Output

Has anyone run across severe problems of using tBigQuery_Output and with identifying to Cloud Storage with Interoperable access.
My conception is that this should be possible with open Data Integration.
I succeed in identifying to the Bigquery but fail with (presumably) Cloud storage identification while code is running SignatureCode Checks. While using tGSBucketExists the identification runs smoothly 
-what am I not getting?

First lines of resulting error

Exception in component tBigQueryOutput_1_tBQBE
org.jets3t.service.ServiceException: Service Error Message. -- ResponseCode: 403, ResponseStatus: Forbidden, XML Error Message: <?xml version='1.0' encoding='UTF-8'?><Error><Code>SignatureDoesNotMatch</Code><Message>The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method.</Message><StringToSign>PUTxwRA/jqrcr+JKHJ9Dbce2A==application/octet-streamWed, 19 Oct 2016 15:11:26 GMTx-goog-meta-md5-hash:"myalpahnumerichash"/beanstalk/biquery_bulk.txt</StringToSign></Error>
at org.jets3t.service.impl.rest.httpclient.RestStorageService.performRequest(RestStorageService.java:400)
Labels (3)
5 Replies
Anonymous
Not applicable
Author

Hi 
Your question is not really clear to me. Are you trying to connect to BigQuery with Google Storage credentials ? 
The message you receive indicates that some security parameters are not the good ones (signature algorithm or certificate). 
fdioum36
Contributor
Contributor

Hi

I have the same problem. I can't write to bigquery

Can I have the issue please ? How do you resolve this ?

McJingles
Contributor III
Contributor III

@fdioum36  can you share the screenshot then I can give the maximum details to resolve your problem...

 

fdioum36
Contributor
Contributor

@McJinglesthanks you for the reply, I resolved the problem by regenering new key into Google (not use the pass in the json file)

sirarm9
Contributor
Contributor

Hi, I've the same issue. Please can you explain me better how you fix this issue? You've regenerated the key. Ok, but how did you fill the parameters in the tbigqueryoutput component?

Thk