没有OpenID端点发现 - 依赖方超时选项 [英] No OpenID endpoint found - Relying Party Timeout Option

查看:242
本文介绍了没有OpenID端点发现 - 依赖方超时选项的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个依靠党和DotNetOpenAuth运行的提供商。问题是,当供应商并没有在一段时间访问它是从IIS卸载以节省内存(这通常是一件好事)。然而,在这种情况下,它会导致依赖方抛出无OpenID端点发现异常。

I have a Relying Party and a provider running with DotNetOpenAuth. The issue is that when the provider has not been accessed in a while it is unloaded from IIS to conserve memory (which is normally a good thing). However, in this case it causes the Relying Party to throw the "No OpenID endpoint found" exception.

我知道IIS可以被构造成从未卸载的应用程序,但不是在这种情况下,一个选择

I know that IIS can be configured to never unload an application, but that is not an option in this case.

有没有增加对依赖方超时让它等到提供商唤醒,而不是扔没有OpenID端点发现异常的方法吗?

Is there a way to increase the timeout on the relying party to let it wait until the provider "wakes up" and not throw the No OpenId Endpoint Found exception?.

我想我的maxAuthenticationTime属性了吧,但我想这是真正为总认证往返应允许采取多少分钟的设置。

I thought I had it with the "maxAuthenticationTime" property, but I guess this is really a setting for how many minutes in total the authentication round trip should be allowed to take.

感谢。

推荐答案

是的,这些超时可以通过你的web.config文件进行配置。下面是一个片段,用默认值,你可以提出:

Yes, these timeouts can be configured via your web.config file. Below is a snippet, with the defaults which you can raise:

   <messaging>
        <untrustedWebRequest
            timeout="00:00:10"
            readWriteTimeout="00:00:01.500"

满配置选项记录

这篇关于没有OpenID端点发现 - 依赖方超时选项的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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