Comments on: Using two Membership Providers for ASP.NET logins

By: David

David — Thu, 15 Dec 2011 15:20:14 +0000

Hi Steve

This does not seem ot be catching the validation, it just uses the default, what have i missed?

Hear from you soon

Dave

By: stevi

stevi — Wed, 02 Nov 2011 17:26:31 +0000

Andrew, I do think your proposed solution has a lot of merit.

By: AndrewH

AndrewH — Wed, 02 Nov 2011 15:31:53 +0000

You could also consider moving this down a layer. You could create a custom provider that wraps the logic of trying multiple stores (through the existing providers.)

By creating a custom provider that wraps the existing providers you need not change the user interface code at all. This centralises your logic and can even be reused between systems, if needs be.

By: Robert J. Bullock

Robert J. Bullock — Mon, 25 Jul 2011 19:22:46 +0000

For some reason, I can’t get to the username/password controls in the Login1_Authenticate event… “LoginBox” isn’t there.

By: Greg

Greg — Tue, 04 Jan 2011 12:24:23 +0000

My login is working but my Page.User.Identity.Name == “”. How do I populate the page User when overriding the Authenticate method like this?

By: stevi

stevi — Mon, 07 Jun 2010 16:59:29 +0000

Paul,
That’s certainly possible, although I’ve yet to see a case of more than two membership providers.

Were I to go to n > 2, I’d probably switch to some sort of factory pattern to handle the various unique elements of each membership provider, to avoid a large if/then or case statement in the Login.Authenticate method.

By: paul

paul — Mon, 07 Jun 2010 15:49:03 +0000

I like your idea, but you know, it’d be even more extensible if you just iterate over your providers, rather than calling those two specifically.

By: MGarfield

MGarfield — Mon, 10 May 2010 19:26:37 +0000

The login code worked perfectly! Thanks for publishing the user login solution. I changed just a few lines but the rest was stright forward.

By: mcm

mcm — Mon, 01 Mar 2010 07:44:26 +0000

work well! thank you!

By: stevi

stevi — Tue, 23 Feb 2010 22:52:00 +0000

David,
Yes, that’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 “SecondarySqlMembershipProvider”