jimwooley | Posts: 6

.Net sdk broken against sandbox due to disabling TLS 1.0

Wednesday, November 15, 2017 at 10:50am
0 votes
According to the comment in this thread from the REST forum, Harris indicates that ESL turned off support for TLS 1.0 this week. This breaks the .Net SDK default implementation because that solution targets .Net 4.5. The fix against the current executable of the SDK is to add the following line when configuring your RslClient: 
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;
I wonder if it makes sense to a) update the SDK to target 4.6.1 instead of 4.5 and/or b) add this call inside of the SDK itself?
FredericDH | Posts: 51

Reply to: .Net sdk broken against sandbox due to disabling TLS 1.0

Wednesday, November 15, 2017 at 10:54am
0 votes
Is it why I am getting since yesterday the following error when creating any package with the .NET SDK? Could not create a new package. Exception: Object reference not set to an instance of an object.
harishaidary | Posts: 1812

Reply to: .Net sdk broken against sandbox due to disabling TLS 1.0

Wednesday, November 15, 2017 at 11:04am
0 votes
@Jim The next release of the SDKs should include this fix. I will double check this and get back to you. @Frederic Yes, that is most probably why. Right now, TLS 1.0 has been disabled on all our sandbox environments. You will need to update to TLS 1.1 and above. This change will happen in production on March 10 2018.
FredericDH | Posts: 51

Reply to: .Net sdk broken against sandbox due to disabling TLS 1.0

Wednesday, November 15, 2017 at 11:06am
0 votes
@Haris, thanks for your quick reply. Any ETA for the updated SDK that will include this fix ?
harishaidary | Posts: 1812

Reply to: .Net sdk broken against sandbox due to disabling TLS 1.0

Wednesday, November 15, 2017 at 11:09am
0 votes
Not at this moment. However, the fix that Jim posted is a one liner that you simply add to your code, for example, right before you create your EslClient.
FredericDH | Posts: 51

Reply to: .Net sdk broken against sandbox due to disabling TLS 1.0

Wednesday, November 15, 2017 at 11:16am
0 votes
For sure, I will use this in the meantime Thanks
willm1716 | Posts: 4

Reply to: .Net sdk broken against sandbox due to disabling TLS 1.0

Thursday, November 16, 2017 at 04:00pm
0 votes
Your blog post called "eSignLive and TLS Communication: What’s The Latest?" states , "NET 3.5 or below: TLS 1.1 and 1.2 are not supported and there is no workaround." This is not accurate. Microsoft added support for TSL 1.1 and 1.2 in 2017 with a Windows update. This issue is a defect in your SDK.
harishaidary | Posts: 1812

Reply to: .Net sdk broken against sandbox due to disabling TLS 1.0

Friday, November 17, 2017 at 04:03am
0 votes
Thanks for the info. I will update my blog post accordingly.

Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off

LoginSign Up