<?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 September 21st changes in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/September-21st-changes/m-p/52170#M27459</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;According to:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Authorize-Net-Begins-Infrastructure-and-SHA-2-Certificate/ba-p/49615" target="_blank"&gt;https://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Authorize-Net-Begins-Infrastructure-and-SHA-2-Certificate/ba-p/49615&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;"To ensure your solution works with the infrastructure changes, please validate the following:&lt;BR /&gt;Your certificate store includes certificates for Root 2 - GeoTrust Global CA&lt;BR /&gt;Your security transport—the part that negotiates TLS—supports SHA-256&lt;BR /&gt;Your solution does not connect directly to Authorize.Net using an IP address&lt;BR /&gt;Your solution’s firewall is not set to whitelist Authorize.Net IP addresses for outbound connections"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;----------------------------------------------------&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1) re: "Your certificate store includes certificates for Root 2 - GeoTrust Global CA"&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our SSL root is "GlobalSign Root CA". Will our current SSL function properly with your changes, or do we have to get a new one with sha2 as well as GeoTrust Global CA root? Please clarify.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://ip1.i.lithium.com/94215a5a000625012ce0ae248858d6a90b1e8a3d/687474703a2f2f6b616d696c62696764612e636f6d2f667470757365722f73736c2e706e67" border="0" alt="" width="440" height="324" /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;2) re: "Your security transport—the part that negotiates TLS—supports SHA-256"&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a&amp;nbsp;new version of the authorize.net dll that we should download and use?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://ip1.i.lithium.com/5170ca5dcd0ea59fa25f84eb2c39e0737d622845/687474703a2f2f6b616d696c62696764612e636f6d2f667470757365722f73736c322e706e67" border="0" alt="" width="424" height="383" /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Based on the above, do we need to make any changes to how we process authorize.net transactions in order for them to continue working on September 21st? Any pointers will be very appreciated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Kamil&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 14 Sep 2015 03:16:56 GMT</pubDate>
    <dc:creator>quantifyip</dc:creator>
    <dc:date>2015-09-14T03:16:56Z</dc:date>
    <item>
      <title>September 21st changes</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/September-21st-changes/m-p/52170#M27459</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;According to:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Authorize-Net-Begins-Infrastructure-and-SHA-2-Certificate/ba-p/49615" target="_blank"&gt;https://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Authorize-Net-Begins-Infrastructure-and-SHA-2-Certificate/ba-p/49615&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;"To ensure your solution works with the infrastructure changes, please validate the following:&lt;BR /&gt;Your certificate store includes certificates for Root 2 - GeoTrust Global CA&lt;BR /&gt;Your security transport—the part that negotiates TLS—supports SHA-256&lt;BR /&gt;Your solution does not connect directly to Authorize.Net using an IP address&lt;BR /&gt;Your solution’s firewall is not set to whitelist Authorize.Net IP addresses for outbound connections"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;----------------------------------------------------&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1) re: "Your certificate store includes certificates for Root 2 - GeoTrust Global CA"&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our SSL root is "GlobalSign Root CA". Will our current SSL function properly with your changes, or do we have to get a new one with sha2 as well as GeoTrust Global CA root? Please clarify.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://ip1.i.lithium.com/94215a5a000625012ce0ae248858d6a90b1e8a3d/687474703a2f2f6b616d696c62696764612e636f6d2f667470757365722f73736c2e706e67" border="0" alt="" width="440" height="324" /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;2) re: "Your security transport—the part that negotiates TLS—supports SHA-256"&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a&amp;nbsp;new version of the authorize.net dll that we should download and use?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://ip1.i.lithium.com/5170ca5dcd0ea59fa25f84eb2c39e0737d622845/687474703a2f2f6b616d696c62696764612e636f6d2f667470757365722f73736c322e706e67" border="0" alt="" width="424" height="383" /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Based on the above, do we need to make any changes to how we process authorize.net transactions in order for them to continue working on September 21st? Any pointers will be very appreciated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Kamil&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 14 Sep 2015 03:16:56 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/September-21st-changes/m-p/52170#M27459</guid>
      <dc:creator>quantifyip</dc:creator>
      <dc:date>2015-09-14T03:16:56Z</dc:date>
    </item>
    <item>
      <title>Re: September 21st changes</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/September-21st-changes/m-p/52181#M27469</link>
      <description>&lt;P&gt;ps. For clarity, we use something like this to process transactions:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;lt;add key="CCAuthLogin" value="somelogin"/&amp;gt;&amp;nbsp;&lt;BR /&gt;&amp;nbsp;&amp;lt;add key="CCAuthTransKey" value="somekey"/&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;and&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;AuthLogin = ConfigurationManager.AppSettings("CCAuthLogin")&amp;nbsp;&lt;BR /&gt;&amp;nbsp;AuthTransKey = ConfigurationManager.AppSettings("CCAuthTransKey")&lt;/P&gt;&lt;P&gt;&amp;nbsp;Dim request As New AuthorizationRequest(CCNum, ExpDate, Amount, Description)&lt;/P&gt;&lt;P&gt;&amp;nbsp;request.Login = AuthLogin&lt;BR /&gt;&amp;nbsp;request.TranKey = AuthTransKey&lt;/P&gt;&lt;P&gt;&amp;nbsp;request.Method = "CC"&lt;BR /&gt;&amp;nbsp;request.Type = "AUTH_CAPTURE"&lt;/P&gt;&lt;P&gt;&amp;nbsp;...&lt;/P&gt;&lt;P&gt;&amp;nbsp;...&lt;/P&gt;&lt;P&gt;Dim gate As New Gateway(AuthLogin, AuthTransKey)&lt;/P&gt;&lt;P&gt;gate.TestMode = False&lt;BR /&gt;Dim response As GatewayResponse&lt;BR /&gt;response = gate.Send(request)&lt;/P&gt;&lt;P&gt;&amp;nbsp;...&lt;/P&gt;&lt;P&gt;&amp;nbsp;...&lt;/P&gt;</description>
      <pubDate>Mon, 14 Sep 2015 17:13:54 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/September-21st-changes/m-p/52181#M27469</guid>
      <dc:creator>quantifyip</dc:creator>
      <dc:date>2015-09-14T17:13:54Z</dc:date>
    </item>
  </channel>
</rss>

