英文:
Why is Ping Federate memberOf attribute causing ERR_HTTP2_PROTOCOL_ERROR
问题
由于公司政策，我在分享信息方面有很大限制...所以请尽量不要对我太苛刻。
我有一个.NET 6 MVC Web应用程序，我已经集成了PingOne。
对于我的组织内的用户，身份验证正在工作。我已添加了"memberOf"属性以获取用户组和额外的信息。
在进行了这些更改后，我尝试再次登录，但出现了以下屏幕。
- 我已经检查了IISExpress日志，没有任何迹象表明有问题。
- 验证了我的响应是否到达Ping，并且他们是否发送了响应。
- 在添加"memberOf"属性后，cookie的大小非常大...约为24,000字节。以前它小于4,000字节。
我想知道是否有人对这个问题有可能的解决方案。如果这是一个HTTP头限制的问题，我会希望看到该错误，但在添加"memberOf"属性后，唯一明显的不同之处似乎是cookie的大小。网站是可以访问的，但在到达Ping并重定向回我的页面后无法访问。
英文:
Due to company policy, I am very limited in what I am able to share.... so please try not to be too tough on me.
I have a .net 6 mvc web application that I have integrated with PingOne.
Authentication is working for users within my organization. I have added the memberOf attribute in order to obtain user groups and additional information.
After that change is in place, I try to login again and I am greeted with the following screen.
- I have checked IISExpress logs and nothing there indicates a problem.
- Verified that my response is reaching ping and they are sending response back.
- Response size of the cookies when adding the memberOf attribute is very large.... ~24,000. Previously it was under 4,000.
I want to know if anyone has any possible solutions to this problem. If it were an http header limit issue, I would expect to see that error but the cookie size is the only significant difference I can gather after the memberOf attribute is added. The site can be reached, just not after it reaches ping and redirects back to my page.
答案1
得分: 0
我通过从 Telerik 下载免费版本的 Fiddler 工具，成功找到了更详细的错误信息。
这确实确认了疑虑，即已达到标头限制。在减小响应大小后，应用程序网站现在可以访问。
英文:
I was able to find out more detailed error information by downloading a free version of the Fiddler tool from telerik.
This indeed did confirm suspicions that the header limit was being reached. After reducing the size of the response the application site is now reachable.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论