Last post Feb 15, 2011 08:28 AM by vaizeman
Feb 03, 2011 11:43 AM|vaizeman|LINK
assume I have a multi layer application with the following logical separation between layer:
Data access layer
I'd like to use a custom asp.net membership provider for authentication/authorization in my app.
which is the best layer where to put the custom asp.net membership provider?
Feb 03, 2011 12:54 PM|lneely|LINK
If you like, you can write your data routines in a separate class and call them from the provider classes, which consequently means the provider exists ONLY in the logic layer, but I personally don't see the point...
Feb 15, 2011 01:32 AM|raringsunny|LINK
I am looking for similar info. Did you get an answer to your question?
Where exactly should I place my authentication class? I was planning to make it part of the BLL but I am not sure if that's the best practice.
Feb 15, 2011 08:28 AM|vaizeman|LINK
my question is still unanswered.
below is a good artcle on the implemetation of a custom provider for Entity framerwok:
citing the author "The Provider interfaces between the Business logic and Data Access" and "The actual concrete implementation of the provider is defined in the
So for the moment in my solution I start building the implementation of the custom provider in the Presentation Layer.
All the logic that concerns the interaction with the db lies in the repository layer and the comunication between the two layer is served by the service layer through the implemention of the request response pattern.
I'm not sure this is the best solution so I hope that somebody more skilled may give an advice.