I am new to this concept after having written my own authentication code in
the past. I'm now trying to get my brain around forms authentication in .net
2.0. So far I'm finding it extreemly restrictive and difficult to implement.
I've gone through a VWD2005 walkthrough of creating a super simple forms
authenticated app. All of a sudden (I'm not sure what I did, I was messing
around with stuff as an experement) it stopped authenticating. I went back
into the ASP.NET config tool and deleted and re-added a test user, but it
won't authenticate the user (returns "attempt was not successful. Please try
again").
So, I start looking into the code and.... there isn't any! How does one
start troubleshooting when there isn't anything to troubleshoot?
I've looked through TONS of posts, but, none of them seem to explain how you
could even begin figuring out what is wrong. Can anyone help point me in the
right direction?
Thanks
Bernie
bernadou - 31 Dec 2005 01:34 GMT
So a follow up here...
When I look in my web.config file to see how the login controll knows what
db to use to authenticate against, there is nothing in the web.config file to
tell it what to do. How does ASP.NET know where to authenticate against?
Shouldn't that setting be somewhere in the web, either in source code of XML
config?
The whole authentication process seems to be hidden. Where/how can you
debug this if you have nothing to work with?
B
> I am new to this concept after having written my own authentication code in
> the past. I'm now trying to get my brain around forms authentication in .net
[quoted text clipped - 16 lines]
> Thanks
> Bernie