Home/ Questions/Q 6121817
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T15:49:37+00:00

Background: I’m incorporating the SqlMembership provider into an existing system where I’m building a

  • 0

Background:

I’m incorporating the SqlMembership provider into an existing system where I’m building a web front end. The Membership database will be kept in a separate database.

Beyond the login account, there’s an additional mapping between the accounts that needs to be in place in the main database in order for an account to be able to log in.

Let’s say that this table gives the user the right to use the system.

My question:

I would like to somehow incorporate this into the provider. Is it possible without too much work? (Or is it better to keep it in the AccountMembershipService class?)
Actually regardless, I’m very interested in learning how to put additional login requirements into the provider.

I’m asking this because when I’ve been looking at creating a custom membership provider earlier it seemed at that time a little bit overwhelming.

In other words:

I want to understand how to extend the Membership Provider classes in general and how to extend the login method (ValidateUser) in particular.

Given the sample ODBC implementation It looks like one simply could subclass the default provider and override ValidateUser calling base.ValidateUser as the first step.
However it may or may not be that simple, and I’d be very happy to hear any first hand experiences from implementing or extending membership providers.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I wanted to do something similar, one of the requirements was to use an Oracle DB, so I implemented the OracleMembership provider, hence I could not waste my time rewriting the hole oracle membership provider (it works pretty fine), the second requirement was to use a custom authorization legacy system. So I realized that the Internet Application template which comes with the MVC 2 or 3 comes with a small implementation of the security for the site, specifically take a look on the AccountMembershipService class. You could move all of these elements out of the MVC app to a separate assembly so you could use it even on a client implementation. The AccountMembershipService uses the Membership provider as the underlying authentication system with the option of using FormsAuthentication.

    So I recommend you to take a look on that implementation. You could put your additional authentication code there so your application would stay cleaner and your don’t need to re-invent the wheel and you have the chance to add your own code.

    best regards

    • 0