Answers.Body: <p>This isn't a <em>full</em> answer, but ... I just had to research this same thing for a client.</p>
  
  <ol>
  <li>Check that your processor config is using the correct URLs:
  <a href="http://www.authorize.net/support/akamaifaqs/#newurls" rel="nofollow">http://www.authorize.net/support/akamaifaqs/#newurls</a></li>
  </ol>
  
  <p>/civicrm/admin/paymentProcessor?reset=1</p>
  
  <ol start="2">
  <li><p>Even in our client's old version of CiviCRM, the transaction ID field is 255 characters. </p></li>
  <li><p>The cipher suite is a question for your host. A good host <em>should</em> be using modern cipher suites and disallowing insecure ones. </p></li>
  <li><p>Not sure about requiring sequential transaction ID ... have not done a CiviCRM code audit to make sure (yet). Don't see why it would, but who knows. </p></li>
  </ol>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-04-22T17:04:48.347Z
Answers.Text: You can use https://www.ssllabs.com to check the cipher suites.
Answers.UserDisplayName: G H
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-04-22T16:17:38.713Z
Answers.LastActivityDate: 2016-04-22T16:17:38.713Z
Answers.UserDisplayName: GHolmes
Answers.Body: <p>See <a href="https://issues.civicrm.org/jira/browse/CRM-16928" rel="nofollow">CRM-16928</a>, a pull request on CiviCRM 4.6 to update <code>core/xml/templates/civicrm_data.tpl</code>. It is marked as fixed/completed as of 4.7.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-26T17:20:33.957Z
Answers.Text: Thanks for the post. It would be helpful for others if you could provide a direct link to this.
Answers.UserDisplayName: William Mortada
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-26T13:10:57.657Z
Answers.LastActivityDate: 2016-05-26T20:48:32.333Z
Answers.LastEditDate: 2016-05-26T20:48:32.333Z
Answers.UserDisplayName: Lesley Evensen
Body: <p>I received a notice from authorize.net telling of changes to the interface. I did not see any comments so I thought I would ask the question. Does the connections to civicrm require any updates because of:</p>
  
  <ul>
  <li>Akamai SureRoute </li>
  <li>Transaction and Batch ID </li>
  <li>RC4 Cipher Disablement</li>
  </ul>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-03-24T13:31:42.747Z
Comments.Text: Thanks for asking... I have the exact same questions...  I'm hoping these changes won't break anything?
Comments.UserDisplayName: Gary Zimmerman
Tags: <authorize.net>
Title: Authorize.net changes
ThreadText: # Authorize.net changes
  
  (Asked by: username_0 on 2016-03-22)
  
  I received a notice from authorize.net telling of changes to the interface. I did not see any comments so I thought I would ask the question. Does the connections to civicrm require any updates because of:
  
  * Akamai SureRoute
  * Transaction and Batch ID
  * RC4 Cipher Disablement
  
  **Tags:** authorize.net
  
  > **Comments:**
  > **username_1**: Thanks for asking... I have the exact same questions...  I'm hoping these changes won't break anything?  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2016-04-22. Score: 3
  
  This isn't a *full* answer, but ... I just had to research this same thing for a client.
  
  1. Check that your processor config is using the correct URLs:
     <http://www.authorize.net/support/akamaifaqs/#newurls>
  
  /civicrm/admin/paymentProcessor?reset=1
  
  2. Even in our client's old version of CiviCRM, the transaction ID field is 255 characters.
  3. The cipher suite is a question for your host. A good host *should* be using modern cipher suites and disallowing insecure ones.
  4. Not sure about requiring sequential transaction ID ... have not done a CiviCRM code audit to make sure (yet). Don't see why it would, but who knows.
  
  > **Comments:**
  > **username_3**: You can use https://www.ssllabs.com to check the cipher suites.  
  
  ---
  
  ### Answer by username_4 on 2016-05-26. Score: 2
  
  See [CRM-16928](https://issues.civicrm.org/jira/browse/CRM-16928), a pull request on CiviCRM 4.6 to update `core/xml/templates/civicrm_data.tpl`. It is marked as fixed/completed as of 4.7.
  
  > **Comments:**
  > **username_5**: Thanks for the post. It would be helpful for others if you could provide a direct link to this.  
  
  ---
  
  