从今天开始AuthenticateWithApp引发NullReferenceException [英] AuthenticateWithApp throwns NullReferenceException since today

查看:59
本文介绍了从今天开始AuthenticateWithApp引发NullReferenceException的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

从今天开始,在.NET-Podio-Client(最新版本1.5.8)中调用AuthenticateWithApp-function时,我们将面临NullReferenceException.

Since today, we are facing a NullReferenceException when calling the AuthenticateWithApp-function in the .NET-Podio-Client (Newest Version 1.5.8).

我在状态网站上看不到Podio-API的更新或任何停机时间.我想这可能是Podio API内部的问题.

I couldn't see an update of the Podio-API or any downtime in the status-website. I guess it must be a problem inside the Podio API.

有人遇到同样的问题吗?

Anybody with the same problem?

关于Thorsten

Regards Thorsten

推荐答案

今天也偶然发现了那个.邮递员工作的Podio .NET库中的请求失败.这是由Podio的API更新引起的,如@Sara所说.似乎我的系统(以及您的系统)仍默认为Tls 1.0

Stumbled upon that one too, today. Requests in postman worked Podio .NET library failed. It's caused by an API update by Podio, like @Sara said. Seems my system (and yours too) still defaults to Tls 1.0

在Main()的开头添加它.这将强制至少Tls 1.1.

Add this at beginning of Main(). This will force at least Tls 1.1.

System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12 | SecurityProtocolType.Tls11;

或者,您也可以设置默认值,如此处所述:

Alternatively you could also set the default like described here:

https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls

这篇关于从今天开始AuthenticateWithApp引发NullReferenceException的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆