C# Jira SDK: The request was aborted: Could not create SSL/TLS secure channel

Jake See_ls6834

I had been using I am using Atlassian.SDK C# v10.3.0 for months until end Jun without problems. Then, I started getting the "Could not create SSL/TLS secure channel" error, so I updated to Atlassian.SDK C# v10.6.0, and added TLS1.2 before calling CreateRestClient:

// server requires TLS1.2 due to vulnerability in older protocols
System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12;
Jira = Jira.CreateRestClient("https://company.atlassian.net", txtUsername.Text, txtPassword.Text);

 And it was able to to connect properly without the error, but then next when I tried to call

var user = Jira.Users.GetUserAsync("admin");
user.Wait(); 

I get an exception with InnerException:

@{"Response Content: <html>\n\n<head>\n \n\n\n\n\n\n <script id=\"@atlassian/spa-iframe-script\" type=\"text/javascript\">\n (function() {\n var spaIframeRegex = /([&?]spaIframe=true*$|spaIframe=true&|[?&]spaIframe=true(?=#))/;\n ...

What is happening and how can I resolve it?

Daniel Eads

Hey Jake,

In addition to dropping TLS 1.0 and 1.1, we've also recently stopped supporting passwords over basic authentication. This change was enforced on all accounts near the end of June, so I think this may be what you're running into.

The short answer is that you'll need to generate an API token at https://id.atlassian.com/manage/api-tokens and drop that in where you've currently got your password stored. The great thing about tokens is that you can assign unique ones per-application, and you can revoke them in the future without having to change your account password.

More details are on this KB article, but for your convenience I've copied over the setup instructions:

1. Log in to https://id.atlassian.com/manage/api-tokens.
2. Click Create API token.
3. From the dialog that appears, enter a memorable and concise Label for your token and click Create.
4. Click Copy to clipboard, then paste the token to your script, or elsewhere to save:
   
   

Note:

• For security reasons it isn't possible to view the token after closing the creation dialog; if necessary, create a new token.
• You should store the token securely, just as for any password.

 

Cheers,
Daniel