nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Cannot view attachment from API. Error TLS/SSL not supported

Ismaël Ayoub

Hello,

I am using the API to get an attachment but it is generating an error of "Request aborted: SSL/TLS not supported"

 ServicePointManager.Expect100Continue = true;
//ServicePointManager.SecurityProtocol = (SecurityProtocolType)3072; //use TLS 1.2
ServicePointManager.SecurityProtocol = SecurityProtocolType.Ssl3 | SecurityProtocolType.Tls | SecurityProtocolType.Tls11 | SecurityProtocolType.Tls12;
ServicePointManager.ServerCertificateValidationCallback += (sender, certificate, chain, sslPolicyErrors) => true;
var client = new RestClient("https://selfdeploy.atlassian.net/secure/attachment/27100/****");
var request = new RestRequest(Method.GET);

request.AddHeader("Content-Type", "application/json");
request.AddHeader("Authorization", "Basic **********");
IRestResponse response = client.Execute(request);

Is there something that I am doing wrong ?

Can someone help please ?

Thanks in advance

Accepted answers

Dario B

Hi @Ismaël Ayoub ,

If I understand correctly you are able to call other JIRA Cloud REST API endpoints but you get an error when you try to download attachments.

However, from above code it is not possible to understand what you are doing and there are chances that the error message is misleading (the problem might be somewhere else). It can indeed be the case that your call is failing to follow the redirect url and therefore to create the channel, but there is nothing wrong with the way you set the TLS protocol in your code.

Therefore, in order to proceed:

Make sure you are following redirects
Check what happens if you do not specify the protocol (some of the url you are redirected to are also accepting TLS 1.3)
If nothing works:
1. let us know which endpoint(s) you are calling
2. Try to call the same endpoint(s) using Curl and paste the output in here.

For example, on my side as long as I follow redirects everything works whether I specify the TLS protocol or not:

1) Downloading an attachment without specifying the protocol (see at some point TLS 1.3 is used):

curl -v -L -u <USERNAME>:<PASSWORD> https://XXXXXXX.atlassian.net/secure/attachment/10005/cannot-quote,list.png -o pic.png

[... REMOVED...]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
[...]
{ [5 bytes data]
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
} [5 bytes data]

< HTTP/2 302 
< server: AtlassianProxy/1.15.8.1
< cache-control: no-cache, no-store, must-revalidate
< content-type: image/png
...
< location: https://api.media.atlassian.com/file/[....]


* Issue another request to this URL: 'https://api.media.atlassian.com/file/[....]
[...]
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
* subject: C=AU; ST=New South Wales; L=Sydney; O=Atlassian Pty Ltd; CN=*.media.atlassian.com
[...]


< HTTP/2 200 
< date: Wed, 06 Nov 2019 15:54:43 GMT
< content-type: image/png
[...]

2) Specifying the protocol:

curl --tlsv1.2 -v -L -u <USERNAME>:<PASSWORD> https://XXXXXXX.atlassian.net/secure/attachment/10005/cannot-quote,list.png -o pic.png
[...]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
[...]

< HTTP/2 302 
[...]

* Connection #0 to host XXXXXXX.atlassian.net left intact
[...]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
[..]

{ [15691 bytes data]
100 37963 100 37963 0 0 47572 0 --:--:-- --:--:-- --:--:-- 9268k
* Connection #1 to host api.media.atlassian.com left intact
..

Cheers,
Dario

All comments

Dario B

Hi @Ismaël Ayoub ,

If I understand correctly you are able to call other JIRA Cloud REST API endpoints but you get an error when you try to download attachments.

Therefore, in order to proceed:

Make sure you are following redirects
Check what happens if you do not specify the protocol (some of the url you are redirected to are also accepting TLS 1.3)
If nothing works:
1. let us know which endpoint(s) you are calling
2. Try to call the same endpoint(s) using Curl and paste the output in here.

For example, on my side as long as I follow redirects everything works whether I specify the TLS protocol or not:

1) Downloading an attachment without specifying the protocol (see at some point TLS 1.3 is used):

curl -v -L -u <USERNAME>:<PASSWORD> https://XXXXXXX.atlassian.net/secure/attachment/10005/cannot-quote,list.png -o pic.png

[... REMOVED...]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
[...]
{ [5 bytes data]
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
} [5 bytes data]

< HTTP/2 302 
< server: AtlassianProxy/1.15.8.1
< cache-control: no-cache, no-store, must-revalidate
< content-type: image/png
...
< location: https://api.media.atlassian.com/file/[....]


* Issue another request to this URL: 'https://api.media.atlassian.com/file/[....]
[...]
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
* subject: C=AU; ST=New South Wales; L=Sydney; O=Atlassian Pty Ltd; CN=*.media.atlassian.com
[...]


< HTTP/2 200 
< date: Wed, 06 Nov 2019 15:54:43 GMT
< content-type: image/png
[...]

2) Specifying the protocol:

curl --tlsv1.2 -v -L -u <USERNAME>:<PASSWORD> https://XXXXXXX.atlassian.net/secure/attachment/10005/cannot-quote,list.png -o pic.png
[...]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
[...]

< HTTP/2 302 
[...]

* Connection #0 to host XXXXXXX.atlassian.net left intact
[...]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
[..]

{ [15691 bytes data]
100 37963 100 37963 0 0 47572 0 --:--:-- --:--:-- --:--:-- 9268k
* Connection #1 to host api.media.atlassian.com left intact
..

Cheers,
Dario

Ismaël Ayoub

Hello @Dario B ,

Thanks for your reply.

I have done what you suggested me to do on curl and here is the results:

Normal:

curl -v -L -u <username>:<password> https://XXXXX.atlassian.net/secure/attachment/27100/XXXXX.xlsx -0 test.xlsx
* Trying xxx.xxx.xxx.xxx...
* TCP_NODELAY set
* Connected to XXXX.atlassian.net (xxx.xxx.xxx.xxx) port 443 (#0)
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* error setting certificate verify locations:
CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* Curl_http_done: called premature == 0
* Closing connection 0
curl: (77) error setting certificate verify locations:
CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* Rebuilt URL to: test.xlsx/
* getaddrinfo(3) failed for test.xlsx:80
* Couldn't resolve host 'test.xlsx'
* Closing connection 1
curl: (6) Couldn't resolve host 'test.xlsx'

Specify protocol:

curl --tlsv1.2 -v -L -u <username>:<password> https://xxxxx.atlassian.net/secure/attachment/27100/CXXXX.xlsx -0 test.xlsx
* Trying xxx.xxx.xxx.xxx...
* TCP_NODELAY set
* Connected to xxxxxx.atlassian.net (xxx.xxx.xxx.xxx) port 443 (#0)
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* error setting certificate verify locations:
CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* Curl_http_done: called premature == 0
* Closing connection 0
curl: (77) error setting certificate verify locations:
CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* Rebuilt URL to: test.xlsx/
* getaddrinfo(3) failed for test.xlsx:80
* Couldn't resolve host 'test.xlsx'
* Closing connection 1
curl: (6) Couldn't resolve host 'test.xlsx'

Actually, I could download the attachment with the link until recently I got this issue.

Here is my code in C#:

As you can see, I am allowing redirect in my code

private HttpClient CreateClient()
{
    var handler = new HttpClientHandler()
    {
        AllowAutoRedirect = true
    };
    HttpClient client = new HttpClient(handler);

    client.BaseAddress = new Uri(this._baseUrl);
    client.DefaultRequestHeaders.Accept.Add(new  MediaTypeWithQualityHeaderValue("application/json"));
    client.DefaultRequestHeaders.Add("X-Atlassian-Token", "no-check");
    client.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Basic XXXXXXXXXXXX");

    return client;
}


public Task<byte[]> GetFile(string url)
{
    Task<byte[]> ret = default(Task<byte[]>);
    using (var client = CreateClient())
    {
       HttpResponseMessage response = client.GetAsync(url).Result;
       response.EnsureSuccessStatusCode();

       Task<byte[]> cntent = response.Content.ReadAsByteArrayAsync();
       cntent.Wait();
       ret = cntent;
    }
    return ret;
}

The response that I got is :

I don't know if I am doing something wrong or there is a something I am looping.

Can you advise please ?

Thanks

Dario B

Hi @Ismaël Ayoub ,

In the Curl output I can see 2 different errors:

Your system seems to be unable to find the certificate verify location (where the trusted certificates are stored on your machine) and therefore it is closing the connection :
```
* error setting certificate verify locations:
CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* Curl_http_done: called premature == 0
* Closing connection 0
```

You use -0 (zero) instead -o (output) and therefore curl thinks that's the url to contact:

* Rebuilt URL to: test.xlsx/
* getaddrinfo(3) failed for test.xlsx:80
* Couldn't resolve host 'test.xlsx'
* Closing connection 1
curl: (6) Couldn't resolve host 'test.xlsx'

Now, it can be that there is a problem with the certificate storage path on the machine where you are running the test from, but if this is the case then you shouldn't be able to connect to any other REST API endpoint as well.

Also, please notice that once again the provided code does not help since is not showing the endpoints called or the logic followed.

Cheers,
Dario

Ismaël Ayoub

Hello @Dario B

The endpoint I am using is the following: https://XXXXX.atlassian.net/secure/attachment/27122/picture.png

I have found that there is a redirection plus there is a verification of the certificate. Here is the details:


* Preparing request to https://XXXXXX.atlassian.net/secure/attachment/27122/picture.png
* Using libcurl/7.57.0-DEV OpenSSL/1.0.2o zlib/1.2.11 libssh2/1.7.0_DEV
* Current time is 2019-11-12T05:16:52.116Z
* Disable timeout
* Enable automatic URL encoding
* Enable SSL validation
* Enable cookie sending with jar of 0 cookies
* Trying xxx.xxx.xxx.xxx...
* TCP_NODELAY set
* Connected to xxxx.atlassian.net (xxx.xxx.xxx.xxx) port 443 (#0)
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
* CAfile: \\file\2017-09-20.pem
* CApath: none
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (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, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
* subject: C=US; ST=California; L=San Francisco; O=Atlassian Network Services, Inc.; CN=*.atlassian.net
* start date: Oct 6 00:00:00 2017 GMT
* expire date: Dec 20 12:00:00 2019 GMT
* subjectAltName: host "xxxx.atlassian.net" matched cert's "*.atlassian.net"
* issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 High Assurance Server CA
* SSL certificate verify ok.
* Server auth using Basic with user <username>

> GET /secure/attachment/27122/picture.png HTTP/1.1
> Host: selfdeploy.atlassian.net
> Authorization: Basic XXXXXXXXX
> Accept: */*

< HTTP/1.1 302 
< Server: AtlassianProxy/1.15.8.1
< Cache-Control: no-cache, no-store, must-revalidate
< Content-Type: image/png
< Strict-Transport-Security: max-age=315360000; includeSubDomains; preload

* Connection #0 to host XXXXXX.atlassian.net left intact
* Issue another request to this URL: '
Headers["Location"]
* Trying xxx.xxx.xxx.xxx...
* TCP_NODELAY set
* Connected to api.media.atlassian.com (xxx.xxx.xxx.xxx) port 443 (#1)
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
* CAfile: \\file\2017-09-20.pem
* CApath: none
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (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, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
* subject: C=AU; ST=New South Wales; L=Sydney; O=Atlassian Pty Ltd; CN=*.media.atlassian.com
* start date: Oct 3 00:00:00 2019 GMT
* expire date: Dec 17 12:00:00 2021 GMT
* subjectAltName: host "api.media.atlassian.com" matched cert's "*.media.atlassian.com"
* issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 High Assurance Server CA
* SSL certificate verify ok.

< HTTP/1.1 200 OK
< date: Tue, 12 Nov 2019 05:15:57 GMT
< content-type: image/png
< content-length: 70812

In my code I have put a condition like:

if(response2.StatusCode == HttpStatusCode.MovedPermanently || response2.StatusCode == HttpStatusCode.Found)

// take the response2.Headers.Location and GetAsync from the URL.

In doing that, I still got the first error from my first post.

Can you help please ?

Thanks in advance.

Ismaël

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud