Re: AuthorizeNet SSL Update

This WebDNA talk-list message is from

2004

It keeps the original formatting. numero = 55489
interpreted = N
texte = Basically, your server has Certificates preinstalled that give the webserver the information to make the secure connection through the =browser.If you have never updated these Global Certificates, then the browser =willreturn an error that it is not from a known trusted source, or even failcompletely. In this case, it only applies to Verisign Certificates, andonly ones that are issued or renewed after the January Date.This link gives instructions for checking what version of the Verisign =Certis installed.https://www.verisign.com/support/site/caReplacement.html>From Microsoft:VeriSign maintains many certificates and certificate revocation lists =(CRLs)that are expiring or that have expired. This is not uncommon. Typically,certificates and CRLs are short-lived by design. However, certificates =aresometimes re-issued to give them a longer life span. This is generally =not aproblem, but it can create issues with servers that use secure socket =layer(SSL) to help protect sessions that connect to their resources.If a server operator installs an SSL certificate from VeriSign, togetherwith the relevant issuing certification authority certificates, and then =theserver operator later renews the SSL certificate through VeriSign, theserver operator must make sure that the intermediate issuing =certificatesare updated at the same time.Sal D'Anna-----Original Message-----From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com] On Behalf OfClint DavisSent: Wednesday, January 14, 2004 11:41 AMTo: WebDNA TalkSubject: AuthorizeNet SSL UpdateDid anyone else see this?What does it mean in English?Verisign recently established a new Root Certificate for SSL =certificates itissues. On January 7, 2004, Verisign=B9s old Root Certificate expired. =As aresult, if you submit transactions to the Authorize.Net Payment Gateway =viaAdvanced Integration Method (AIM), and currently have Verisign=B9s old =RootCertificate installed on your Web server, your connection to theAuthorize.Net Payment Gateway may have been temporarily broken.To correct the problem, Authorize.Net received a new certificate fromVerisign and you should now be able to successfully submit transactions.However, you must manually update your Web server software to includesupport for Verisign=B9s new Root Certificate prior to February 9, 2004.Failure to do so may result in further connection difficulties.If your Web site uses any Java applications, pleaseseehttp://sunsolve.sun.com/pub-cgi/retrieve.pl?doc=3Dfsalert%2F57436&zone=_32=3D57436 for detailed information on resolving this issue.If you use a Web hosting service, please contact your service provider =forinformation regarding their plans to update their server software to =includesupport for Verisign=B9s new Root Certificate. You may also need to =contactyour company=B9s Web Developer or Systems Engineer for assistance.For more information about how to resolve this issue, pleaseseehttp://www.verisign.com/support/vendors/exp-gsid-ssl.html or contactVerisign Customer Support.To download and install a copy of Verisign=B9s new Root Certificate, =pleaseseehttps://www.verisign.com/support/site/caReplacement.html.-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail toWeb Archive of this list is at: http://webdna.smithmicro.com/-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

Re: AuthorizeNet SSL Update ( Clint Davis 2004)
Re: AuthorizeNet SSL Update ( "Sal" 2004)
Re: AuthorizeNet SSL Update ( Clint Davis 2004)
AuthorizeNet SSL Update ( Clint Davis 2004)

Basically, your server has Certificates preinstalled that give the webserver the information to make the secure connection through the =browser.If you have never updated these Global Certificates, then the browser =willreturn an error that it is not from a known trusted source, or even failcompletely. In this case, it only applies to Verisign Certificates, andonly ones that are issued or renewed after the January Date.This link gives instructions for checking what version of the Verisign =Certis installed.https://www.verisign.com/support/site/caReplacement.html>From Microsoft:VeriSign maintains many certificates and certificate revocation lists =(CRLs)that are expiring or that have expired. This is not uncommon. Typically,certificates and CRLs are short-lived by design. However, certificates =aresometimes re-issued to give them a longer life span. This is generally =not aproblem, but it can create issues with servers that use secure socket =layer(SSL) to help protect sessions that connect to their resources.If a server operator installs an SSL certificate from VeriSign, togetherwith the relevant issuing certification authority certificates, and then =theserver operator later renews the SSL certificate through VeriSign, theserver operator must make sure that the intermediate issuing =certificatesare updated at the same time.Sal D'Anna-----Original Message-----From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com] On Behalf OfClint DavisSent: Wednesday, January 14, 2004 11:41 AMTo: WebDNA TalkSubject: AuthorizeNet SSL UpdateDid anyone else see this?What does it mean in English?Verisign recently established a new Root Certificate for SSL =certificates itissues. On January 7, 2004, Verisign=B9s old Root Certificate expired. =As aresult, if you submit transactions to the Authorize.Net Payment Gateway =viaAdvanced Integration Method (AIM), and currently have Verisign=B9s old =RootCertificate installed on your Web server, your connection to theAuthorize.Net Payment Gateway may have been temporarily broken.To correct the problem, Authorize.Net received a new certificate fromVerisign and you should now be able to successfully submit transactions.However, you must manually update your Web server software to includesupport for Verisign=B9s new Root Certificate prior to February 9, 2004.Failure to do so may result in further connection difficulties.If your Web site uses any Java applications, pleaseseehttp://sunsolve.sun.com/pub-cgi/retrieve.pl?doc=3Dfsalert%2F57436&zone=_32=3D57436 for detailed information on resolving this issue.If you use a Web hosting service, please contact your service provider =forinformation regarding their plans to update their server software to =includesupport for Verisign=B9s new Root Certificate. You may also need to =contactyour company=B9s Web Developer or Systems Engineer for assistance.For more information about how to resolve this issue, pleaseseehttp://www.verisign.com/support/vendors/exp-gsid-ssl.html or contactVerisign Customer Support.To download and install a copy of Verisign=B9s new Root Certificate, =pleaseseehttps://www.verisign.com/support/site/caReplacement.html.-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail toWeb Archive of this list is at: http://webdna.smithmicro.com/-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ "Sal"

DOWNLOAD WEBDNA NOW!

Re: AuthorizeNet SSL Update

2004

Top Articles:

Related Readings: