generateSharedAccessSignature returning date in wrong format

Which service(blob, file, queue, table) does this issue concern?

blob

Which version of the SDK was used?

2.10.2

What’s the Node.js/Browser version?

8.11.1

What problem was encountered?

generateSharedAccessSignature when used returning 403 make sure header is formatted correctly

Steps to reproduce the issue?

I have this code:

var azure = require('azure-storage');

module.exports = function(context, req) {
  if (req.body.container) {
    // The following values can be used for permissions:
    // "a" (Add), "r" (Read), "w" (Write), "d" (Delete), "l" (List)
    // Concatenate multiple permissions, such as "rwa" = Read, Write, Add
    context.res = generateSasToken(
      context,
      req.body.container,
      req.body.blobName,
      req.body.permissions
    );
  } else {
    context.res = {
      status: 400,
      body: "Specify a value for 'container'"
    };
  }

  context.done(null, context);
};

function generateSasToken(context, container, blobName, permissions) {
  var connString = process.env.AzureWebJobsStorage;
  var blobService = azure.createBlobService(connString);

  // Create a SAS token that expires in an hour
  // Set start time to five minutes ago to avoid clock skew.
  var startDate = new Date();
  startDate.setMinutes(startDate.getMinutes() - 5);
  var expiryDate = new Date(startDate);
  expiryDate.setMinutes(startDate.getMinutes() + 60);

  permissions = permissions || azure.BlobUtilities.SharedAccessPermissions.READ + azure.BlobUtilities.SharedAccessPermissions.WRITE;

  var sharedAccessPolicy = {
    AccessPolicy: {
      Permissions: permissions,
      Start: startDate,
      Expiry: expiryDate
    }
  };

  var sasToken = blobService.generateSharedAccessSignature(
    container,
    blobName,
    sharedAccessPolicy
  );

  context.log(sasToken);

  return {
    token: sasToken,
    uri: blobService.getUrl(container, blobName, sasToken, true)
  };
}

BUt the date in the return token looks different if I go into the portal and create a token:

Portal token looks like this:

?sv=2018-03-28&ss=b&srt=sco&sp=rwdlac&se=2019-01-30T23:19:06Z&st=2019-01-30T15:19:06Z&spr=https&sig=xxxxxxx

response returned from generateSharedAccessSignature

st=2019-01-30T16%3A19%3A12Z&se=2019-01-30T17%3A19%3A12Z&sp=racw&sv=2018-03-28&sr=c&sig=AhtXpqFfhCnUjwcN5SBcA2hAZw0P35S32QeoTLeEWvQ%3D

The dates look different and the sig looks completely different also.

Have you found a mitigation/solution?

[Prussia]

Hey, man. What is the resolution? I have a similar issue.

[dagda1]

i’m sorry that does not make a lot of sense to me. all i want to do is returns a sas token to my website users can upload files. my permissions are in the right order but i get the 403. can you please help how to do this. i don’t understand what i have to do and i can’t find any useful information. i’m coming from aws where everything just works to azure which is horrific. lots of out of date docs and code and no real pointers how to do anything. it is really depressing