Customizations and configuration of DotNetOpenAuth behavior. Options for general messaging protocols, such as whitelist/blacklist hosts and maximum message age. Restrictions and settings to apply to outgoing HTTP requests to hosts that are not trusted by this web site. Useful for OpenID-supporting hosts because HTTP connections are initiated based on user input to arbitrary servers. A set of host names (including domain names) to allow outgoing connections to that would otherwise not be allowed based on security restrictions. The host name to trust. For example: "localhost" or "www.mypartners.com". The host name to NOT trust. For example: "localhost" or "www.mypartners.com". Clears all hosts from the whitelist. A set of host names (including domain names) to disallow outgoing connections to that would otherwise be allowed based on security restrictions. The host name known to add to the blacklist. For example: "localhost" or "www.mypartners.com". The host name known to remove to the blacklist. For example: "localhost" or "www.mypartners.com". Clears all hosts from the blacklist. The maximum time to allow for an outgoing HTTP request to complete before giving up. The maximum time to allow for an outgoing HTTP request to either send or receive data before giving up. The maximum bytes to read from an untrusted server during an outgoing HTTP request before cutting off the response. The maximum redirection instructions to follow before giving up. The type that implements the DotNetOpenAuth.IEmbeddedResourceRetrieval interface to instantiate for obtaining URLs that fetch embedded resource streams. Primarily useful when the System.Web.UI.Page class is not used in the ASP.NET pipeline. The fully-qualified name of the type that implements the IEmbeddedResourceRetrieval interface. The maximum time allowed between a message being sent to when it is received before it is considered expired. The maximum time to consider a safe difference in server clocks. Whether remote parties will be held strictly to the protocol specifications. Strict will require that remote parties adhere strictly to the specifications, even when a loose interpretation would not compromise security. true is a good default because it shakes out interoperability bugs in remote services so they can be identified and corrected. But some web sites want things to Just Work more than they want to file bugs against others, so false is the setting for them. Whether SSL requirements within the library are disabled/relaxed. Use for TESTING ONLY. The maximum allowable size for a 301 Redirect response before we send a 200 OK response with a scripted form POST with the parameters instead in order to ensure successfully sending a large payload to another server that might have a maximum allowable size restriction on its GET request. The maximum age of a secret used for private signing or encryption before it is renewed. Configuration for OpenID authentication (relying parties and providers). Configuration specific for OpenID relying parties. Security settings that apply to OpenID relying parties. The OpenID Provider Endpoint (aka "OP Endpoint") that this relying party trusts. A value indicating whether any login attempt coming from an OpenID Provider Endpoint that is not on this whitelist of trusted OP Endpoints will be rejected. If the trusted providers list is empty and this value is true, all assertions are rejected. Restricts OpenID logins to identifiers that use HTTPS throughout the discovery process, and only uses HTTPS OpenID Provider endpoints. Optionally restricts interoperability with remote parties that implement older versions of OpenID. Shared associations with OpenID Providers will only be formed or used if they are willing to form associations equal to or greater than a given level of protection. Shared associaitons with OpenID Providers will only be formed or used if they are willing to form associations equal to or less than a given level of protection. Requires that OpenID identifiers upon which authentication requests are created are to be OP Identifiers. Claimed Identifiers are not allowed. Requires that the relying party can form a shared association with an OpenID Provider before creating an authentication request for it. Note that this does not require that the Provider actually use a shared association in its response. Requires that users begin their login experience at the relying party rather than at a Provider or using other forms of unsolicited assertions. Requires that the claimed identifiers used to log into the relying party be the same ones that are originally issued by the Provider. Makes it impossible for the relying party to read authentication response extensions that are not signed by the Provider. Controls whether identifiers that are both OP Identifiers and Claimed Identifiers should ever be recognized as claimed identifiers. Controls whether certain Claimed Identifiers that exploit features that .NET does not have the ability to send exact HTTP requests for will still be allowed by using an approximate HTTP request. Only impacts hosts running under partial trust. Controls whether the relying party should take special care to protect users against replay attacks when interoperating with OpenID 1.1 Providers. Manipulates the set of custom behaviors that are automatically applied to incoming and outgoing OpenID messages. The fully-qualified name of the type that implements the IRelyingPartyBehavior interface. The fully-qualified name of the type that implements the IRelyingPartyBehavior interface. Adds or removes OpenID discovery mechanisms to use on OpenID identifiers. The fully-qualified name of the type that implements the IIdentifierDiscoveryService interface. Customizes the non-standard host-meta discovery process, when that discovery service is enabled. Allows DotNetOpenAuth to remember X509Certificates that it has already verified are valid to avoid validating them each time. Use when operating on a server with long delays when validating certificates. A custom implementation of IRelyingPartyApplicationStore to use by default for new instances of OpenIdRelyingParty. A fully-qualified type name of the custom implementation of IRelyingPartyApplicationStore. Whether "dnoa.userSuppliedIdentifier" is tacked onto the openid.return_to URL in order to preserve what the user typed into the OpenID box. Configuration specific for OpenID providers. Security settings that apply to OpenID providers. Sets maximum ages for shared associations of various strengths. The OpenID association type (i.e. HMAC-SHA1 or HMAC-SHA256) The lifetime a shared association of this type will be used for. The OpenID association type (i.e. HMAC-SHA1 or HMAC-SHA256) Requires that relying parties' realm URLs be protected by HTTPS, ensuring that the RP discovery step is not vulnerable to DNS poisoning attacks. Provides automatic security protections to OpenID 1.x relying parties so security is comparable to OpenID 2.0 relying parties. Whether the Provider should ease the burden of storing associations by encoding their secrets (in signed, encrypted form) into the association handles themselves, storing only a few rotating, private symmetric keys in the Provider's store instead. The level of verification done on a claimed identifier before an unsolicited assertion for that identifier is issued by this Provider. The claimed identifier being asserted must delegate to this Provider and this must be verifiable by the Provider to send the assertion. The claimed identifier being asserted is checked for delegation to this Provider and an warning is logged, but the assertion is allowed to go through. The claimed identifier being asserted is not checked to see that this Provider has authority to assert its identity. The minimum shared association strength to form with relying parties. The maximum shared association strength to form with relying parties. Manipulates the set of custom behaviors that are automatically applied to incoming and outgoing OpenID messages. The fully-qualified name of the type that implements the IRelyingPartyBehavior interface. A custom implementation of IProviderApplicationStore to use by default for new instances of OpenIdRelyingParty. A fully-qualified type name of the custom implementation of IProviderApplicationStore. Adjusts the list of known OpenID extensions via the registration of extension factories. The fully-qualified name of the type that implements IOpenIdExtensionFactory. The fully-qualified name of the type that implements IOpenIdExtensionFactory. Controls XRI resolution to XRDS documents. Controls whether XRI identifiers are allowed at all. The XRI proxy resolver to use for obtaining XRDS documents from an XRI. The maximum time a user can take at the Provider while logging in before a relying party considers the authentication lost. Whether the results of identifier discovery should be cached for a short time to improve performance on subsequent requests, at the potential risk of reading stale data. Settings for OAuth consumers and service providers. Settings applicable to OAuth Consumers. Security settings applicable to OAuth Consumers. Settings applicable to OAuth Service Providers. Security settings applicable to OAuth Service Providers. Optionally restricts interoperability with OAuth consumers that implement older versions of OAuth. The initial version of OAuth, now known to be vulnerable to certain social engineering attacks. The OAuth version that protects against social engineering attacks by introducing the oauth_verifier parameter. The maximum time allowed for users to authorize a consumer before request tokens expire. Sets the custom type that implements the INonceStore interface to use for nonce checking. A fully-qualified type name of the custom implementation of INonceStore. Settings OAuth 2 clients, authorization servers and resource servers. Settings applicable to OAuth 2 Clients. The maximum time a user can take at the authorization server before the client considers the authorization lost. Settings applicable to OAuth 2 Authorization Servers. The fully-qualified name of the ClientAuthenticationModule-derived type. The fully-qualified name of the ClientAuthenticationModule-derived type. Settings applicable to OAuth 2 Resource Servers. Adjusts statistical reports DotNetOpenAuth may send to the library authors to assist with future development of the library. Controls whether reporting is active at all or entirely inactive. Note that even if active, the reports may be more or less empty based on other settings. Controls how frequently reports are collected and transmitted. Controls how frequently the statistics that are collected in memory are persisted to disk. Whether a list of features in DotNetOpenAuth that are actually used by this host are included in the report. Whether a set of counters that track how often certain events (such as an successful or failed authentication) is included in the report. Whether to include a few of this host's URLs that contain DotNetOpenAuth components. Whether to include the cultures as set on the user agents of incoming requests to pages that contain DotNetOpenAuth components.