--->In my Web.config file, loginUrl is set to "Login.aspx". So all the unauthenticated request will go to Login.aspx page, right?
Yes, provided you have set authorization in web.config to deny anonymous(?) users.
1) How does the application lead a user to default.aspx page when a user enters correct pwd?
defaultUrl is the attribute that results into redirect to default.aspx if no ReturnUrl is present in the querystring. Its default value is "default.aspx". Check the link below:
http://msdn.microsoft.com/en-us/library/1d3t3c61.aspx2) Now when I run the application and if my pwd is correct, the application redirects me to the SecuredPages.aspx. What's going on here?
---> Here ReturnUrl in the querystring of your url is playing some role here.
Say you directly navigate to Login.aspx via a link then the ReturnUrl should be empty and you will be taken to defaultUrl after authentication.
But say your try to access SecuredPage.aspx then you will first be taken to login.aspx with ReturnUrl querystring parameter added to your login.aspx url. Upon successful login your will be redirected to the ReturnUrl i.e. Securepage.aspx
---->and why do I need to created SecuredPage folder in this example?
can you explain that a bit.