Trouble Generating SAS Token for Blob Storage

[mohammedp010]

area

/area runtime

Question

Hey folks, I ran into a bit of a roadblock while building my app with Dapr and wanted to share what’s going on — maybe you’ve seen something similar or have some guidance?

---

Trouble Generating SAS Token for Blob Storage

What’s the deal?:

I am using Azure Blob Storage, which—as you probably know—needs a SAS token to access files securely. The bindings.azure.blobstorage binding in Dapr currently supports basic operations like get, create, delete, and list, but doesn’t seem to directly support generating SAS tokens.

What I have tried:

I gave it a shot by tweaking the metadata in our requests, hoping I could trigger SAS token generation that way. Here’s what I did:

• 1 with get – here I receive the file data:

{
  "operation": "get",
  "metadata": {
    "sasToken": "true",
    "blobName": "<filename>"
  }
}

• 2 with create – here I receive the presigned URL:

{
  "operation": "create",
  "metadata": {
    "sasToken": "true",
    "blobName": "<filename>"
  }
}

Where I am at::

It looks like Dapr doesn’t currently support SAS token generation directly, at least not in a straightforward way. If there’s a trick I am missing, I’d love to hear it. Otherwise, maybe this could be something to consider as a future enhancement?

Let me know what you think — any tips or workarounds are more than welcome!

---

[yaron2]

sasToken is not a supported metadata right now. This is a essentially a feature request for this component. I actually have a commit that enables this in my local branch, but currently its not prioritized for the upcoming release. However, this is a perfectly valid feature addition to the component.

[alicejgibbons]

Duplicate of #3484 which ended up going stale so lets use this one to track.