Hi everyone, just wondering if you could please help. I have a website that I would like to have a basic login control in. I know I could set up all the sql SP's and tables and all done - done that plenty of times, but for this particular website I know I'll just have the one user who a). needs to get access to some pages that others shouldn't and b). change some content.
So my basic question is that how (un)secure it is to have a 'pseudo' log in - basically if I set up a password that's stored in the code behind page and it gets checked against what the user inputs, and then if they are the same I give some extra cabailities. I couls set it up with a session state to make sure the password doesn't get automatically put in for bots (like 5 attempts max, etc).
What do you think. Besides losing a whole lot of built in capabilities of the asp security features, which I don't really need, what are the downfalls for this? The upside is really that that the client wi ...
Go to the complete details ...