-
Notifications
You must be signed in to change notification settings - Fork 80
Don't force TLS 1.0 #29
Comments
I will check it. Unfortunately now there is no time and I can not say when the result will be. Thank you for message. |
This must be why linkedin has stopped working! https://developer.linkedin.com/docs/guide/v2/concepts/authentication
|
Any chance of fixing this anytime soon? |
I wonder if the TLS 1.2 protocol issue was ever resolved for LinkedIn login... I tried to comment the line: However, it did not resolve the issue... EDIT: Correction - after recompiling either of the lines in bold above works! |
Anytime this will get fixed? |
Still doesn't work. More and more services are TLS 1.2 only so this is a real show-stopper |
Guys, its pretty easy to fix by yourself: File: OAuthUtility.cs, Line around 495 var securityProtocol = ServicePointManager.SecurityProtocol;
|
Hi,
In ExecuteRequest nemiro.oauth is forcing the use of TLS 1.0 as security protocol.
This make impossible to connect to web servers that only support TLS 1.1/1.2 failing with "An existing connection was forcibly closed by the remote host".
One quick fix is simply replacing that line with:
ServicePointManager.SecurityProtocol |= SecurityProtocolType.Tls;
So that it will allow TLS 1.0 while still keeping the other protocols enabled.
But I think that don't enabling TLS 1.0 at all would be the a wiser way to go. I don't think that a library should touch ServicePointManager.SecurityProtocol.
The text was updated successfully, but these errors were encountered: