DotNetOpenId can be configured in some aspects inside your web project's - web.config file. To do this, add the below <sectionGroup> within the - <configSections> of your Web.config file:
-<configSections>
- <sectionGroup name="dotNetOpenId">
- <section name="relyingParty" type="DotNetOpenId.Configuration.RelyingPartySection" requirePermission="false" allowLocation="true"/>
- <section name="provider" type="DotNetOpenId.Configuration.ProviderSection" requirePermission="false" allowLocation="true"/>
- <section name="untrustedWebRequest" type="DotNetOpenId.Configuration.UntrustedWebRequestSection" requirePermission="false" allowLocation="false"/>
- </sectionGroup>
-</configSections>If you do not already have a configSections element in your Web.config file, add - it at the very top, as the first child of the root <configuration> tag.
-Following is an example of every possible configuration setting, where each - demonstrate value happens to be the default that would be used if it wasn't set - in the .config file. Keep in mind that every setting below is optional, so - you need only include those elements that you wish to change in your own copy of - Web.config. The <dotNetOpenId> node below should show up as a peer node to - system.web in your Web.config file.
-<dotNetOpenId>
- <relyingParty>
- <security minimumHashBitLength="160" maximumHashBitLength="256"
- requireSsl="false" minimumRequiredOpenIdVersion="V10" />
- <store type="SomeSite.CustomRPStore, SomeSite" />
- </relyingParty>
- <provider>
- <security minimumHashBitLength="160" maximumHashBitLength="256" />
- <store type="SomeSite.CustomProviderStore, SomeSite" />
- </provider>
- <untrustedWebRequest readWriteTimeout="00:00:00.800" timeout="00:00:10" maximumBytesToRead="1048576" maximumRedirections="10">
- <whitelistHosts>
- <add name="localhost" />
- <add name="127.0.0.1" />
- </whitelistHosts>
- <whitelistHostsRegex>
- <add name="^(.*\.)?goodsite.com" />
- </whitelistHostsRegex>
- <blacklistHosts>
- <add name="internalfinancialserver" />
- <add name="www.evilsite.com" />
- </blacklistHosts>
- <blacklistHostsRegex>
- <add name="^(.*\.)?evilsite.com" />
- </blacklistHostsRegex>
- </untrustedWebRequest>
-</dotNetOpenId>
-All these configuration values are also configurable at runtime using the object - model of the library. Using the Web.config file allows changes to be made - without recompiling the web site. In the case of OpenIdRelyingParty and - OpenIdProvider, it also allows you to setup your configuration just once, in - your .config file, and have it apply to every instance of OpenIdRelyingParty or - OpenIdProvider instead of you having to set up that configuration everywhere you - instantiate these types.
-By using the ASP.NET <location> element, you can set some configuration settings - for OpenIdRelyingParty or OpenIdProvider based on which directory or web page in - your project is instantiating them. This would allow you to, for example, - use enhanced SSL security requirements at just the administrator log in screen - while allowing non-SSL OpenIDs for ordinary users.
- - - diff --git a/doc/README.html b/doc/README.html index 7877d7219c..a82d84824d 100644 --- a/doc/README.html +++ b/doc/README.html @@ -4,8 +4,8 @@DotNetOpenAuth is a .NET library that enables OpenID, OAuth and InfoCard support to be easily added to your web and/or desktop applications.
The project site for this library is hosted at - - http://dotnetopenid.googlecode.com/. Please visit that web site for + + http://dotnetopenauth.net/. Please visit that web site for documentation, support and maintenance releases.
As with any library that is used for security-sensitive purposes such as authentication and authorization, you should periodically check the project web diff --git a/doc/WebFarms.htm b/doc/WebFarms.htm index 44447e7fc9..5ae924d310 100644 --- a/doc/WebFarms.htm +++ b/doc/WebFarms.htm @@ -7,21 +7,26 @@
- DotNetOpenId works without being a part of an ASP.NET web site. The - ASP.NET controls may not be used in this context, but the programmatic access to - the OpenIdProvider and OpenIdRelyingParty classes will work correctly if you - call the method overloads that do not require a current ASP.NET context. - The xml doc comments indicate which methods require an ASP.NET context and which - methods may be used without one.
+ DotNetOpenAuth works without being a part of an ASP.NET web site. The ASP.NET + controls may not be used in this context, but the programmatic access to the OpenIdProvider + and OpenIdRelyingParty classes will work correctly if you call the method overloads + that do not require a current ASP.NET context. The xml doc comments indicate + which methods require an ASP.NET context and which methods may be used without one.- If your web servers need to use proxy servers to make outbound requests, you - will need to configure your .NET AppDomain to default to the proxy server you - require so that DotNetOpenId will use it. + If your web servers need to use proxy servers to make outbound requests, you will + need to configure your .NET AppDomain to default to the proxy server you require + so that DotNetOpenAuth will use it.
- To set the default web proxy, set the System.Net.WebRequest.DefaultWebProxy + To set the default web proxy programmatically, set the System.Net.WebRequest.DefaultWebProxy property.
+
+ To use the default proxy using your web.config file, add this section:
+
<system.net> + <defaultProxy enabled="true" /> +</system.net>+