We're using Marketo's webhook to connect with a vendor. Today I was notified by this vendor they're "going to be shutting off anything that uses SSLv3 and TLSv1.1, so it is advised we switch to using TLSv1.2 at this time." Any one else run into this issue?
You are quite right. The webhook client side won't support servers that are locked to only TLSv1.2 at this time. If you're going to lose connectivity immediately you could use a proxy temporarily (the proxy runs TLSv1.1 to/from you and TLSv1.2 to/from upstream).
And Rajesh Talele Aruba Prod too
Marketo Webhooks have been upgraded with the Feb 5th release to support TLS 1.1 and 1.2. The immediate reason was the announcement that SFDC would stop supporting TLS 1.0 on Production orgs on March 4, 2017 (1 year from now). However, SFDC will be upgrading sandboxes sooner, and you can elect to upgrade your sandboxes today, so we wanted to be ready for that.
I don't know the details of the Feb 5th release, other than that it supports SFDC's new setup (which I believe still supports 1.1). It may be that a 1.2-only connection does not work yet (as Sanford's tests indicate).
The corresponding "Critical Update" is already available in production instances of SFDC and can be "updated" at any moment by the SFDC admin who would not necessary know it would impact Marketo. So good news Marketo has been upgraded. The date of March 2017 is the deadline at which, if the SFDC have not activated the upgrade, it will be automatically updated by SFDC.