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

Access Linked Storage Account #277

Open
chewsonCVE opened this issue Aug 19, 2019 · 1 comment
Open

Access Linked Storage Account #277

chewsonCVE opened this issue Aug 19, 2019 · 1 comment

Comments

@chewsonCVE
Copy link

Trying to avoid saving storage keys either in the environment or within the code base. Is there any way to either exposed the key for a storage account linked to the batch account or to stage files directly to the linked account in the SDK? I am currently pulling a separate token from AD w/ the identity model, but it would be nice to just do this once with the batch account.

@bgklein
Copy link
Contributor

bgklein commented Aug 19, 2019

The current recommended way to authenticate with other services from a node deployed with Batch is to upload a certificate to Batch (https://docs.microsoft.com/en-us/rest/api/batchservice/certificate/add), specify that certificate to be downloaded to your nodes(https://docs.microsoft.com/en-us/rest/api/batchservice/pool/add#request-body), and then use that certificate to authenticate with a Service Principal which has access to desired services.

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

No branches or pull requests

2 participants