Using curl to access Azure Storage Container failure

Question

Using curl to access Azure Storage Container failure

Liz Wendland 0

Hi,

I would like to use the Azure Storage API but the simplest things are not working for me.

curl -i --verbose \

-H "Content-Type: application/x-www-form-urlencoded" \

-d "grant_type=client_credentials&client_id=${APP_ID}&client_secret=${PASSWORD}&resource=https%3A%2F%2Fstorage.azure.com%2F" \

"https://login.microsoftonline.com/${TENANT_ID}/oauth2/token" \

-X POST

This does produce a token (access_token) But when I try to use it:

curl -i --verbose --oauth2-bearer "${access_token}" -H 'x-ms-version: 2019-12-12' \ "https://<mystorageprovider>.blob.core.windows.net/?comp=list"

Results in 400: BAD REQUEST

Any ideas?

1 answer

Your answer

Answer 1

Bhanu Ejjagiri 261 Microsoft Employee

Hi Liz Wendland,
Thanks for reaching Microsoft Q&A team.

Based on the error "400: Bad request" - it is a client-side issue or could be due to an incorrect formation of the API call.

Can you try the below once, and let me know the status.

curl -i --verbose -H 'x-ms-version: 2019-12-12' \

"https://<storage-account-name>.blob.core.windows.net/?comp=list" \

-H "Authorization: Bearer ${access_token}"

Thanks!

Liz Wendland 0

Dear Bhanu,

I have been able to work around the issue by using the Ruby gem Faraday to interact with the Azure API. I am using all the same credentials, urls etc. Perhaps curl or my shell is adding something that Azure is unhappy with? I am using bash on Ubuntu23.04. At any rate, I was only using curl to simplify things for me while I figure out how to call the API. I guess that backfired. :)

So, I can close this question but I will paste the output of that command in case you find it useful.

$ curl -i --verbose -H 'x-ms-version: 2019-12-12' "https://mystorage.blob.core.windows.net/?comp=list" -H "Authorization: Bearer ${access_token}"
*   Trying 52.239.170.36:443...
* Connected to mystorage.blob.core.windows.net (52.239.170.36) port 443 (#0)
* ALPN: offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN: server did not agree on a protocol. Uses default.
* Server certificate:
*  subject: CN=*.blob.core.windows.net
*  start date: Sep 27 13:49:40 2023 GMT
*  expire date: Sep 27 13:49:40 2024 GMT
*  subjectAltName: host "mystorage.blob.core.windows.net" matched cert's "*.blob.core.windows.net"
*  issuer: C=US; O=Microsoft Corporation; CN=Microsoft RSA TLS CA 01
*  SSL certificate verify ok.
* using HTTP/1.x
> GET /?comp=list HTTP/1.1
> Host: mystorage.blob.core.windows.net
> User-Agent: curl/7.88.1
> Accept: */*
> x-ms-version: 2019-12-12
> Authorization: Bearer eyJ0*******
> 
< HTTP/1.1 400 Bad Request
HTTP/1.1 400 Bad Request
< Content-Type: text/html; charset=us-ascii
Content-Type: text/html; charset=us-ascii
< Server: Microsoft-HTTPAPI/2.0
Server: Microsoft-HTTPAPI/2.0
< Date: Thu, 05 Oct 2023 13:36:19 GMT
Date: Thu, 05 Oct 2023 13:36:19 GMT
< Connection: close
Connection: close
< Content-Length: 311
Content-Length: 311
< 
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Bad Request</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Bad Request</h2>
<hr><p>HTTP Error 400. The request is badly formed.</p>
</BODY></HTML>
* Closing connection 0
* TLSv1.2 (OUT), TLS alert, close notify (256):

Bhanu Ejjagiri 261 Reputation points Microsoft Employee

2023-10-17T17:29:57.6633333+00:00

Hi Liz Wendland
Thanks for your update and glad that you found an alternative, and thanks for the curl output.

At this point, it is quite strange and the cause for this simple curl command to fail is unknown. I would recommend you contact support, so if you have a support plan, I request you file a support ticket, else please do let us know, we will try and help you get a one-time free technical support.

In this case, could you send an email to AzCommunity[at]Microsoft[dot]com referencing this thread as well as your subscription ID. Please mention "ATTN subm" in the subject field. Thank you for your cooperation on this matter and look forward to your reply.

Share via

Using curl to access Azure Storage Container failure

1 answer

Your answer