AuthenticationFailed - "The Date header in the request is incorrect."

[gzzengwei]

Hi

I have it working before like few weeks before and now I had this AuthenticationFailed for all requests.

to re-produce:

mix new my_app

and in mix.exs

  defp deps do
    [
      {:azurex, "~> 0.1.2"}
    ]
  end

and in config/config.exs

config :azurex, Azurex.Blob.Config,
  storage_account_name: System.get_env("AZURE_STORAGE_ACCOUNT"),
  storage_account_key: System.get_env("AZURE_STORAGE_ACCESS_KEY")

and run the code

Azurex.Blob.list_containers 

and I got

{:error,
 %HTTPoison.Response{
   body: "\uFEFF<?xml version=\"1.0\" encoding=\"utf-8\"?><Error><Code>AuthenticationFailed</Code><Message>Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.\nRequestId:e5a8dd0f-e01e-000c-17f1-3fd423000000\nTime:2021-05-03T07:57:39.5168256Z</Message><AuthenticationErrorDetail>The Date header in the request is incorrect.</AuthenticationErrorDetail></Error>",
   headers: [
     {"Content-Length", "419"},
     {"Content-Type", "application/xml"},
     {"Server", "Microsoft-HTTPAPI/2.0"},
     {"x-ms-request-id", "e5a8dd0f-e01e-000c-17f1-3fd423000000"},
     {"x-ms-error-code", "AuthenticationFailed"},
     {"Date", "Mon, 03 May 2021 07:57:38 GMT"}
   ],
   request: %HTTPoison.Request{
     body: "",
     headers: [
       {"authorization",
        "SharedKey xxxxxstorage:4nHSO+J19veoXUZRAXIpRbKbVQV2rS2+0wlhACky35Y="},
       {"x-ms-version", "2019-12-12"},
       {"x-ms-date", "Mon, 03 May 2021 07:57:38 Etc/UTC"}
     ],
     method: :get,
     options: [],
     params: %{},
     url: "https://xxxxxstorage.blob.core.windows.net/?comp=list"
   },
   request_url: "https://xxxxxstorage.blob.core.windows.net/?comp=list",
   status_code: 403
 }}

I suspected it's related to Timex as it did work for me before.

[gzzengwei]

follow up:

I tested the timex version one by one, current azurex@0.1.2 will work with timex@3.7.1 , it breaks from timex@3.7.2

[suranyami]

Slightly better PR #20

[jakobht]

Thanks for the issue, I see that Timex had at breaking change at 3.7.1 -> 3.7.3, which fits with your investigation, see
https://github.com/bitwalker/timex/blob/master/CHANGELOG.md#potentially-breaking
I hope to look at the PR during today.