Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Utilize HMAC access ID/secret keys instead of JSON authentication file #127

Open
ghost opened this issue Jul 30, 2020 · 2 comments
Open

Comments

@ghost
Copy link

ghost commented Jul 30, 2020

Hello,

Is there any way we can utilize HMAC access id and secret key rather than passing the authentication JSON? I tried to find documentation on this but wasn't able to find anything. I saw a mention of setting environmental variables for this but couldn't find much. Overall, it would be preferable to pass these as regular variables instead.

Thanks,
Santosh

@ghost ghost changed the title Utilize HMAC access ID/secret keys instead of JSON Utilize HMAC access ID/secret keys instead of JSON authentication file Jul 30, 2020
@MarkEdmondson1234
Copy link
Collaborator

MarkEdmondson1234 commented Jul 31, 2020

I haven't heard of HMAC before, I found this. https://cloud.google.com/storage/docs/authentication/hmackeys

There are signed URLs for authenticated access, does that suit your use case?
http://code.markedmondson.me/googleCloudStorageR/reference/gcs_signed_url.html

@MarkEdmondson1234
Copy link
Collaborator

There are some examples here on how to create the HTTP headers
https://cloud.google.com/storage/docs/migrating#authentication

You could perhaps look at generating those using curl or otherwise, if I have some working examples I can look at then they can be built using googleAuthR etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant