From cfe204a3ef79c781de06ee0131788543756ea026 Mon Sep 17 00:00:00 2001 From: Laryn Date: Tue, 28 Jul 2015 10:47:20 -0400 Subject: [PATCH] Update Authorize.net to new Akamai URL. --- templates/CRM/Admin/Form/Setting/Url.hlp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/templates/CRM/Admin/Form/Setting/Url.hlp b/templates/CRM/Admin/Form/Setting/Url.hlp index e0fa910108..10bfbd8771 100644 --- a/templates/CRM/Admin/Form/Setting/Url.hlp +++ b/templates/CRM/Admin/Form/Setting/Url.hlp @@ -37,7 +37,7 @@ {/htxt} {htxt id='id-verify_ssl'}

{ts}This setting will verify the SSL certificates received when making secure HTTPS connections to payment processors.{/ts}

-

{ts}For example, in order to process a payment through Authorize.net, CiviCRM must make a request to https://secure.authorize.net/gateway/transact.dll. Using https to connect to secure.authorize.net insures that the connection is encrypted, but it's possible that CiviCRM is actually connecting to an attacker and the attacker is connecting to secure.authorize.net.{/ts}

+

{ts}For example, in order to process a payment through Authorize.net, CiviCRM must make a request to https://secure2.authorize.net/gateway/transact.dll. Using https to connect to secure2.authorize.net insures that the connection is encrypted, but it's possible that CiviCRM is actually connecting to an attacker and the attacker is connecting to secure2.authorize.net.{/ts}

{ts}Verifying the SSL certificate helps confirm that CiviCRM is securely communicating directly to payment processors.{/ts}

{/htxt} -- 2.25.1