Answers.Body: <p>CiviCRM will communicate with AuthorizeNet using whatever versions of TLS are enabled on your server. </p>
  
  <p>To see if your server is using TLS 1.2, go to <a href="https://www.ssllabs.com/ssltest" rel="nofollow noreferrer">https://www.ssllabs.com/ssltest</a> and put in your url </p>
  
  <p>in the Configuration section of the report it will list the TLS versions supported.  <a href="https://i.sstatic.net/6Vjdv.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/6Vjdv.png" alt="enter image description here"></a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-27T04:22:46.590Z
Answers.Text: I also just found this little one liner that will tell you what versions are available on your server
  `openssl ciphers -v | awk '{print $2}' | sort | uniq`
  but it seems to print all those available and not only those enabled. 
  the machine in the image above that has only 1.2 enabled gave this result 
  `$ openssl ciphers -v | awk '{print $2}' | sort | uniq`
  `SSLv3
  TLSv1
  TLSv1.2`
Answers.UserDisplayName: ericG
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-29T08:02:15.417Z
Answers.Text: When CiviCRM is making a request to Authorize.net (transaction setup & submission), it's PHP that requires support for TLS v1.2. When Authorize.net is making a request to CiviCRM (eg IPN), it's your webserver (or SSL terminator) that requires TLS v1.2. The SSLLabs test covers only the second of those scenarios; the former can be found in the output of `phpinfo()` or `php -i | grep -i tls`. **For most servers these will be the same** (in which case the `openssl` test is fine), but you really want to be checking the CiviCRM-to-Authorize.net route IMO. Or just run a test transaction 
Answers.UserDisplayName: Chris Burgess
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-30T03:02:05.800Z
Answers.Text: a big +1 for the extra info and details. Thanks Chris
Answers.UserDisplayName: ericG
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-26T18:50:22.240Z
Answers.LastActivityDate: 2018-01-26T18:50:22.240Z
Answers.UserDisplayName: ericG
Body: <p>Authorize.net will disable older protocols, TLS 1.0 and TLS 1.1, which are highly vulnerable to security breaches. They will be disabled by Authorize.Net on February 28, 2018</p>
  
  <p>What type of protocol and API connection does CiviCRM use?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-01-27T22:08:32.087Z
Comments.Text: This question might be deemed a duplicate of https://civicrm.stackexchange.com/questions/19503/authorize-net-tls-disablement-notice-civicrm?rq=1
Comments.UserDisplayName: petednz - fuzion
Tags: <authorize.net>
Title: what type of protocol and api connection is used for authorize.net
ThreadText: # what type of protocol and api connection is used for authorize.net
  
  (Asked by: username_0 on 2018-01-25)
  
  Authorize.net will disable older protocols, TLS 1.0 and TLS 1.1, which are highly vulnerable to security breaches. They will be disabled by Authorize.Net on February 28, 2018
  
  What type of protocol and API connection does CiviCRM use?
  
  **Tags:** authorize.net
  
  > **Comments:**
  > **username_0**: This question might be deemed a duplicate of https://civicrm.stackexchange.com/questions/19503/authorize-net-tls-disablement-notice-civicrm?rq=1  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2018-01-26. Score: 1 | Accepted answer
  
  CiviCRM will communicate with AuthorizeNet using whatever versions of TLS are enabled on your server.
  
  To see if your server is using TLS 1.2, go to <https://www.ssllabs.com/ssltest> and put in your url
  
  in the Configuration section of the report it will list the TLS versions supported. [![enter image description here](https://i.sstatic.net/6Vjdv.png)](https://i.sstatic.net/6Vjdv.png)
  
  > **Comments:**
  > **username_1**: I also just found this little one liner that will tell you what versions are available on your server `openssl ciphers -v | awk '{print $2}' | sort | uniq` but it seems to print all those available and not only those enabled.  the machine in the image above that has only 1.2 enabled gave this result  `$ openssl ciphers -v | awk '{print $2}' | sort | uniq` `SSLv3 TLSv1 TLSv1.2`  
  > **username_2**: When CiviCRM is making a request to Authorize.net (transaction setup & submission), it's PHP that requires support for TLS v1.2. When Authorize.net is making a request to CiviCRM (eg IPN), it's your webserver (or SSL terminator) that requires TLS v1.2. The SSLLabs test covers only the second of those scenarios; the former can be found in the output of `phpinfo()` or `php -i | grep -i tls`. **For most servers these will be the same** (in which case the `openssl` test is fine), but you really want to be checking the CiviCRM-to-Authorize.net route IMO. Or just run a test transaction   
  > **username_1**: a big +1 for the extra info and details. Thanks Chris  
  
  ---
  
  