REST API URL上的TLS版本 [英] TLS version on REST API URL
问题描述
我尝试在Docusign支持处开票，但他们却以这种方式发送给我。我希望有人能够对此提供帮助。
I tried opening a ticket with Docusign Support, but they sent me this way instead. I'm hoping someone will be able to assist with this.
从11月16日美国中部时间12:30开始，我们开始在我们的应用程序日志中发现错误非生产环境。经调查，看来 https://demo.docusign.net/restapi 开始响应TLSv1查询
Starting on Nov. 16th at about 12:30 Central, we started getting errors in our application logs in our non-production environment. Upon investigation, it appears that https://demo.docusign.net/restapi started responding to TLSv1 queries with the following:
{
"errorCode": "TLS_INVALID_VERSION",
"message": "TLS Version is invalid, please update to TLS1.2 TLSv1.2 is
required. Currently using TLSv1"
}
考虑到Docusign应该在几个月前在其非生产环境中禁用TLSv1，这令我们感到惊讶。那时，我们在上述URL上测试了应用程序（在假定的切换之后），并且一切都在与我们的应用程序一起工作，因此我们假设在应该切换时，生产将继续工作。它做到了。
This came as a surprise to us considering that Docusign was supposed to disable TLSv1 in their non-production environment many months ago. Back then, we tested our application against the above URL (after the supposed switchover) and everything was working with our application, so we assumed that production would continue to work when that was supposed to switch over. And it did.
问题在于，事实证明，Docusign似乎并没有禁用TLSv1，这使我们之前所做的任何测试无效。而现在，我们面临着生产环境在未来某个未知时刻出现故障的风险。
The issue is that it turns out that Docusign seems to have not disabled TLSv1 when they said they were supposed to, which invalidated any testing we did previously. And now, we're at risk of our production environment failing at some unknown point in the future.
那么，有人知道Docusign何时将切换生产环境以禁用TLSv1吗？我们正在研究更新应用程序中的库的选项，以便它们至少支持TLS 1.1，但这可能需要一些时间，这对我们来说是一个关键问题。
So, does anyone know when Docusign will be switching over the production environment so that TLSv1 is disabled? We're investigating the option to update the libraries in the app so they support at least TLS 1.1, but that may take some time and this is a critical issue for us.
休
ps附带说明，该网站说TLS v1.2是必需的，但它仍会响应TLS v1.1。
p.s. On a side note, the site says that TLS v1.2 is required, but it still responds to TLS v1.1.
推荐答案
请注意，公开宣布的TLS 1.0弃用日期为6/25/2018。但是我们有一个宽限期。现在硬性日期即将到来。 PROD中的硬块日期设置为1/31/2019。正如您所注意到的，在演示中，它的11/16。
Note the publicly announced date for TLS 1.0 deprecation is 6/25/2018. However we had a grace period. Now the hard block dates are coming up. The hard block date in PROD is set at 1/31/2019. In Demo its 11/16, as you noticed.
这篇关于REST API URL上的TLS版本的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
