First, let me state that I'm still learning the whole membership provider thing. Up until now, I've stuck with the old model of querying a DB account and storing everything in a user session. I'm a bit behind the curve here. I should also say that I'm not looking for code, but a high level "do X, Y, and Z" explanation.
I'm building a webapp that will use FormsAuthentication to limit access to portions of the website, but in this particular case no specifically defined user database exists. The webserver (WS2008) is in our AD, and all authorized users will have AD accounts. Here's the catch...not everyone with an AD account should have access rights, and the ONLY resource I have for identifying the authorized "login" users are the NTFS permissions of the folder that actually contains the web files. Before you suggest that I simply turn off anonymous authentication, I have to explain that the same application DOES have many fil ...
Go to the complete details ...