<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: TLS1.2 Issue with Authorize.Net Nuget Package in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/TLS1-2-Issue-with-Authorize-Net-Nuget-Package/m-p/58039#M32715</link>
    <description>&lt;P&gt;I tried the solution described here and it seemed to solve the issue:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.developer.cybersource.com/t5/Integration-and-Testing/Sandbox-issues-The-underlying-connection-was-closed-An/m-p/57887#M32569" target="_blank"&gt;https://community.developer.authorize.net/t5/Integration-and-Testing/Sandbox-issues-The-underlying-connection-was-closed-An/m-p/57887#M32569&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am targeting .NET 4.5.0 and adding this line of code:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;   System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12;&lt;/PRE&gt;&lt;P&gt;solved the issue. &amp;nbsp;I added it right before the request to get the AuthNetHostToken. &amp;nbsp;Now I just gotta figure out where it's actually supposed to go in order for all the AuthNet API requests to use TLS1.2&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I also updated to the latest AuthNetSDK package available via NugetPackageManager.&lt;/P&gt;</description>
    <pubDate>Wed, 10 May 2017 16:55:11 GMT</pubDate>
    <dc:creator>ksanchezssmci1</dc:creator>
    <dc:date>2017-05-10T16:55:11Z</dc:date>
    <item>
      <title>TLS1.2 Issue with Authorize.Net Nuget Package</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/TLS1-2-Issue-with-Authorize-Net-Nuget-Package/m-p/58036#M32712</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our .Net Code base is set up to target .Net 4.6.2 which supports TLS1.2 by default. We are using the AuthorizeNet Nuget Package 1.9.2 (latest) to communicate with Authorize.Net. I believe the Nuget package is not yet upgraded to support TLS1.2. This is affecting our Dev, Test and UAT environments very severely right now. How soon can we expect a new upgraded package? Is there a workaraound that we can use for the time being?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Reji&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 10 May 2017 15:29:49 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/TLS1-2-Issue-with-Authorize-Net-Nuget-Package/m-p/58036#M32712</guid>
      <dc:creator>rdasan2017</dc:creator>
      <dc:date>2017-05-10T15:29:49Z</dc:date>
    </item>
    <item>
      <title>Re: TLS1.2 Issue with Authorize.Net Nuget Package</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/TLS1-2-Issue-with-Authorize-Net-Nuget-Package/m-p/58039#M32715</link>
      <description>&lt;P&gt;I tried the solution described here and it seemed to solve the issue:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.developer.cybersource.com/t5/Integration-and-Testing/Sandbox-issues-The-underlying-connection-was-closed-An/m-p/57887#M32569" target="_blank"&gt;https://community.developer.authorize.net/t5/Integration-and-Testing/Sandbox-issues-The-underlying-connection-was-closed-An/m-p/57887#M32569&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am targeting .NET 4.5.0 and adding this line of code:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;   System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12;&lt;/PRE&gt;&lt;P&gt;solved the issue. &amp;nbsp;I added it right before the request to get the AuthNetHostToken. &amp;nbsp;Now I just gotta figure out where it's actually supposed to go in order for all the AuthNet API requests to use TLS1.2&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I also updated to the latest AuthNetSDK package available via NugetPackageManager.&lt;/P&gt;</description>
      <pubDate>Wed, 10 May 2017 16:55:11 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/TLS1-2-Issue-with-Authorize-Net-Nuget-Package/m-p/58039#M32715</guid>
      <dc:creator>ksanchezssmci1</dc:creator>
      <dc:date>2017-05-10T16:55:11Z</dc:date>
    </item>
    <item>
      <title>Re: TLS1.2 Issue with Authorize.Net Nuget Package</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/TLS1-2-Issue-with-Authorize-Net-Nuget-Package/m-p/58040#M32716</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.developer.cybersource.com/t5/user/viewprofilepage/user-id/21523"&gt;@rdasan2017&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Another developer on GitHub suggested you can update&amp;nbsp;your code to specify the default and fallback TLS versions, assuming you're using .NET 4.5.2 or greater: &amp;nbsp;&lt;A href="https://github.com/AuthorizeNet/sdk-dotnet/issues/178" target="_blank"&gt;https://github.com/AuthorizeNet/sdk-dotnet/issues/178&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Richard&lt;/P&gt;</description>
      <pubDate>Wed, 10 May 2017 16:53:03 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/TLS1-2-Issue-with-Authorize-Net-Nuget-Package/m-p/58040#M32716</guid>
      <dc:creator>RichardH</dc:creator>
      <dc:date>2017-05-10T16:53:03Z</dc:date>
    </item>
    <item>
      <title>Re: TLS1.2 Issue with Authorize.Net Nuget Package</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/TLS1-2-Issue-with-Authorize-Net-Nuget-Package/m-p/58043#M32719</link>
      <description>&lt;P&gt;Thanks for the solution. That worked. But I would still like to know if there is a chance that this would be fixed in the Nuget Package itself. I see that there is a PR up for it. (&lt;A href="https://github.com/AuthorizeNet/sdk-dotnet/pull/177" target="_blank"&gt;https://github.com/AuthorizeNet/sdk-dotnet/pull/177&lt;/A&gt;) Just wondering if there would be a updated package with the TLS fix up anytime soon.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Reji&lt;/P&gt;</description>
      <pubDate>Wed, 10 May 2017 18:10:54 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/TLS1-2-Issue-with-Authorize-Net-Nuget-Package/m-p/58043#M32719</guid>
      <dc:creator>rdasan2017</dc:creator>
      <dc:date>2017-05-10T18:10:54Z</dc:date>
    </item>
    <item>
      <title>Re: TLS1.2 Issue with Authorize.Net Nuget Package</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/TLS1-2-Issue-with-Authorize-Net-Nuget-Package/m-p/58181#M32851</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.developer.cybersource.com/t5/user/viewprofilepage/user-id/7546"&gt;@RichardH&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Would you have any updates on my request of Nuget Package Update?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Reji&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 May 2017 21:25:55 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/TLS1-2-Issue-with-Authorize-Net-Nuget-Package/m-p/58181#M32851</guid>
      <dc:creator>rdasan2017</dc:creator>
      <dc:date>2017-05-22T21:25:55Z</dc:date>
    </item>
  </channel>
</rss>

