Databases
StackOverflow2013
Postsdbo
POAuthenticating against multiple flaky Membership providers?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAuthenticating against multiple flaky Membership providers?
    primarykey
    data
    text
    <p>Currently my asp.net app has 5 ActiveDirectoryMembershipProvider and 1 SqlMembershipProvider. Both of those numbers are bound to increase at least some in the near future. The problem is that some of the domains we are authenticating against are flaky. So one out of the 5 might be unreachable for 30 min on Sunday for example. When a user from any provider tries to login during that time they can't do it because the Providers collection throws an error. So if one is down, they are all down. Not fun.</p> <p>I have tried about 72 different ways to approach this and haven't had any luck. Here are my top 3.</p> <p>1: add them all in web.config, override login control authenticate and loop through all Membership.Providers. ValidateUser until we have a match. Works great unless the above mentioned issue. If one is down, the collection poops out and no one gets in.</p> <p>B. Only authenticate against default provider. Have user pick which provider to use and change that to default provider using WebConfigurationManager. Pretty great except for that you are actually changing the web.config file at runtime... Oops! Did I do that?</p> <p>III. Custom provider that checks domain user wants to login with, and in the Initiate() supply appropriate config values from source other than web.config. DB table with all the separate providers info. Then we always ValidateUser on the custom provider, who then checks user picked domain/provider, plugs info in and off we go. This works except if I logout and then login with a diff domain... I can't do that because it's already initialized to the other domain you picked before.</p> <p>Maybe I am missing something easy? I hope so. StackOverflow, you're my only hope.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. US0010
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POAuthenticating against multiple flaky Membership providers?
      1. USKonstantin Chernov
      1. VTFavorite
    2. VO
      singulars
      1. POAuthenticating against multiple flaky Membership providers?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POAuthenticating against multiple flaky Membership providers?
      1. USWayne Cornish
      1. VTFavorite
    1. CO"If I authenticated against any provider - I'm in" - is it true in your case?
      singulars
      1. POAuthenticating against multiple flaky Membership providers?
      1. USKonstantin Chernov
    2. COYes, as long as you can authenticate to one of the providers, we let you in. The app controls what you see from there.
      singulars
      1. POAuthenticating against multiple flaky Membership providers?
      1. US0010
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload