<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Using two Membership Providers for ASP.NET logins</title>
	<atom:link href="http://www.stevideter.com/2008/03/20/using-two-membership-providers-for-aspnet-logins/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.stevideter.com/2008/03/20/using-two-membership-providers-for-aspnet-logins/</link>
	<description>Technology, code, and thoughts by Stevi Deter</description>
	<lastBuildDate>Tue, 23 Feb 2010 22:52:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: stevi</title>
		<link>http://www.stevideter.com/2008/03/20/using-two-membership-providers-for-aspnet-logins/comment-page-1/#comment-9820</link>
		<dc:creator>stevi</dc:creator>
		<pubDate>Tue, 23 Feb 2010 22:52:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevideter.com/2008/03/20/using-two-membership-providers-for-aspnet-logins/#comment-9820</guid>
		<description>David,
Yes, that&#039;s pretty much what I was doing in the case where this came up. 

The default membership provider was the System.Web.Security.ActiveDirectoryMembershipProvider. 

Only if that attempt to authorize fail would the Login control attempt to use the System.Web.Security.SqlMembershipProvider, which was listed in system.web/membership/providers in the web.config with the name &quot;SecondarySqlMembershipProvider&quot;</description>
		<content:encoded><![CDATA[<p>David,<br />
Yes, that&#8217;s pretty much what I was doing in the case where this came up. </p>
<p>The default membership provider was the System.Web.Security.ActiveDirectoryMembershipProvider. </p>
<p>Only if that attempt to authorize fail would the Login control attempt to use the System.Web.Security.SqlMembershipProvider, which was listed in system.web/membership/providers in the web.config with the name &#8220;SecondarySqlMembershipProvider&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://www.stevideter.com/2008/03/20/using-two-membership-providers-for-aspnet-logins/comment-page-1/#comment-9819</link>
		<dc:creator>David</dc:creator>
		<pubDate>Tue, 23 Feb 2010 22:42:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevideter.com/2008/03/20/using-two-membership-providers-for-aspnet-logins/#comment-9819</guid>
		<description>Was wondering... would this work with windows integrated auth on the page?

So, asp.net tried to auth using windows integrated/AD first, then fall back to SQL integrated?

Or am I missing some detail?</description>
		<content:encoded><![CDATA[<p>Was wondering&#8230; would this work with windows integrated auth on the page?</p>
<p>So, asp.net tried to auth using windows integrated/AD first, then fall back to SQL integrated?</p>
<p>Or am I missing some detail?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stevi</title>
		<link>http://www.stevideter.com/2008/03/20/using-two-membership-providers-for-aspnet-logins/comment-page-1/#comment-1038</link>
		<dc:creator>stevi</dc:creator>
		<pubDate>Thu, 02 Apr 2009 17:16:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevideter.com/2008/03/20/using-two-membership-providers-for-aspnet-logins/#comment-1038</guid>
		<description>Cdr. Beavis,

Correct. In your system.web/membership/providers section of your web.config, use the add element to configure your membership providers, one element per provider. Then set the default provider in your membership element, &quot;defaultProvider&quot; attribute.</description>
		<content:encoded><![CDATA[<p>Cdr. Beavis,</p>
<p>Correct. In your system.web/membership/providers section of your web.config, use the add element to configure your membership providers, one element per provider. Then set the default provider in your membership element, &#8220;defaultProvider&#8221; attribute.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cdr. Beavis</title>
		<link>http://www.stevideter.com/2008/03/20/using-two-membership-providers-for-aspnet-logins/comment-page-1/#comment-1032</link>
		<dc:creator>Cdr. Beavis</dc:creator>
		<pubDate>Thu, 02 Apr 2009 04:08:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevideter.com/2008/03/20/using-two-membership-providers-for-aspnet-logins/#comment-1032</guid>
		<description>So, I&#039;m assuming that I just add &quot;SecondarySqlMembershipProvider&quot; into the  section of the  element in the web.config?

Thanks,
-B</description>
		<content:encoded><![CDATA[<p>So, I&#8217;m assuming that I just add &#8220;SecondarySqlMembershipProvider&#8221; into the  section of the  element in the web.config?</p>
<p>Thanks,<br />
-B</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stevi</title>
		<link>http://www.stevideter.com/2008/03/20/using-two-membership-providers-for-aspnet-logins/comment-page-1/#comment-221</link>
		<dc:creator>stevi</dc:creator>
		<pubDate>Fri, 05 Sep 2008 20:45:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevideter.com/2008/03/20/using-two-membership-providers-for-aspnet-logins/#comment-221</guid>
		<description>xuhui,
Thanks for letting me know it was useful to you!</description>
		<content:encoded><![CDATA[<p>xuhui,<br />
Thanks for letting me know it was useful to you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: xuhui</title>
		<link>http://www.stevideter.com/2008/03/20/using-two-membership-providers-for-aspnet-logins/comment-page-1/#comment-220</link>
		<dc:creator>xuhui</dc:creator>
		<pubDate>Fri, 05 Sep 2008 20:42:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevideter.com/2008/03/20/using-two-membership-providers-for-aspnet-logins/#comment-220</guid>
		<description>Very good implementation. I used it in my app. thanks.</description>
		<content:encoded><![CDATA[<p>Very good implementation. I used it in my app. thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Duck Under &#187; Using two ASP.NET membership providers</title>
		<link>http://www.stevideter.com/2008/03/20/using-two-membership-providers-for-aspnet-logins/comment-page-1/#comment-59</link>
		<dc:creator>Duck Under &#187; Using two ASP.NET membership providers</dc:creator>
		<pubDate>Thu, 17 Jul 2008 08:08:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevideter.com/2008/03/20/using-two-membership-providers-for-aspnet-logins/#comment-59</guid>
		<description>[...] Recently I wanted to give someone access to one of my teaching web sites. They were not a student or faculty member so they didn&#8217;t have an account in our active directory. I am not a system administrator so I wasn&#8217;t able to add them to the active directory either. The solution was to add a second membership provider to my ASP.NET site. The first membership provider is based on active directory. The new, 2nd provider is a SQL provider. I found a great blog post that had the relevant code for checking the username and password against the second provider: http://www.stevideter.com/2008/03/20/using-two-membership-providers-for-aspnet-logins/. [...]</description>
		<content:encoded><![CDATA[<p>[...] Recently I wanted to give someone access to one of my teaching web sites. They were not a student or faculty member so they didn&#8217;t have an account in our active directory. I am not a system administrator so I wasn&#8217;t able to add them to the active directory either. The solution was to add a second membership provider to my ASP.NET site. The first membership provider is based on active directory. The new, 2nd provider is a SQL provider. I found a great blog post that had the relevant code for checking the username and password against the second provider: <a href="http://www.stevideter.com/2008/03/20/using-two-membership-providers-for-aspnet-logins/" rel="nofollow">http://www.stevideter.com/2008/03/20/using-two-membership-providers-for-aspnet-logins/</a>. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Using two membership providers - Duck Bytes</title>
		<link>http://www.stevideter.com/2008/03/20/using-two-membership-providers-for-aspnet-logins/comment-page-1/#comment-24</link>
		<dc:creator>Using two membership providers - Duck Bytes</dc:creator>
		<pubDate>Sat, 03 May 2008 23:10:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevideter.com/2008/03/20/using-two-membership-providers-for-aspnet-logins/#comment-24</guid>
		<description>[...] post that had the relevant code for checking the username and password against the second provider: http://www.stevideter.com/2008/03/20/using-two-membership-providers-for-aspnet-logins/.The code&#160;behind for the login page&#160;was in C# so I thought I would provide the bare bones [...]</description>
		<content:encoded><![CDATA[<p>[...] post that had the relevant code for checking the username and password against the second provider: <a href="http://www.stevideter.com/2008/03/20/using-two-membership-providers-for-aspnet-logins/.The" rel="nofollow">http://www.stevideter.com/2008/03/20/using-two-membership-providers-for-aspnet-logins/.The</a> code&nbsp;behind for the login page&nbsp;was in C# so I thought I would provide the bare bones [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
