Click here to Skip to main content
13,086,264 members (67,983 online)
Rate this:
Please Sign up or sign in to vote.
See more:
Do you guys have any samples or links for this issue?
Posted 25-Nov-12 21:51pm
Rate this: bad
Please Sign up or sign in to vote.

Solution 1

Use Authentication & Authorization Concept

ASP.NET authentication and authorization[^] Click Here
Rate this: bad
Please Sign up or sign in to vote.

Solution 2

There is a problem here, in that if you don't use the Membership classes in some form then you have to check and enforce the access rules manually in each and every page. If you use Membership, then it is all handled for you on a folder-by-folder basis via the web.config settings. If you don't, then the configuration is ignored, and you have to do it yourself - this can lead to mistakes and security holes.

Have you considered implementing your own custom Membership provider? It's not complicated, and it does get rid of a lot of the hassles with a brew-your-own-security system.
Have a look at these:
MSDN: Implementing a Membership Provider[^]
Custom MembershipProvider and RoleProvider Implementations that use Web Services[^]
OriginalGriff 26-Nov-12 4:54am
Membership classes are not particularly slow - they are almost certainly faster than any security system you might introduce!

It's not the number of expected valid users you should concern yourself with. It's the one, solitary invalid user you want to worry about...

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS
Top Experts
Last 24hrsThis month

Advertise | Privacy |
Web01 | 2.8.170813.1 | Last Updated 26 Nov 2012
Copyright © CodeProject, 1999-2017
All Rights Reserved. Terms of Service
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100