Hey all, in my login control, i can specify the page i want the user to go to if the login was sucessful, but what if the user clicked on a login-required page, then sucessfully logged in, but it throws them back to the page that i set... how would i make it send them to the page they wanted to go to originally?     

By default, the login control will redirect the user to the requested page if authentication is successful. Your specification of what page to send them to overwrites that built-in function. One solution would be to remove the specification that you declared.

I removed that, and now it takes me to Default.aspx, instead of the intended page.

Hi

Could you please paste the code snippet so that we can find some clue?

XiaoYong Dai – MSFT:

Hi

Could you please paste the code snippet so that we can find some clue?

<asp:Login ID="Login1" runat="server" BackColor="#C2D0E0" BorderColor="#6780B8" BorderStyle="Solid" BorderWidth="1px" LoginButtonImageUrl="~/images/login.gif" LoginButtonType="Image">

</asp:Login>

Nothing special about this... searched the document, and default.aspx is nowhere in there...

Just for the record if anyone else has things set up like me...  I figured out a way to fix this.

In the page that redirects to the login page, put in the page_load:

If not user.identity.isauthenticated = true then

response.redirect("Login.aspx?ReturnPage=MyPage.aspx?ifyouhaveaquery=" & Whatever.text)

Then in the login page (since we know they ARENT logged in) in the page_load

If user.identity.isauthenticated = true then

response.redirect(Request.querystring("ReturnPage"))

Pretty easy when ya think about it :)

I know this post is a little out-dated, but for those of you who stumble onto this issue - I found that I was missing a piece of the picture.  Josh's comment above stating "By default, the login control will redirect the user to the requested page if authentication is successful." is accurate - so long as you're not trying to manually complete the authentication redirection process. 

First, make sure you've eliminated anonymous access to the page the user is attempting to navigate to at the web.config level:

        <authorization>
            <deny users="?"/>
        </authorization>

Now, if you've got any type of Membership-checking redirection functionality written into the Page_Load of your user's destination - something similar to the following, take it out:

        if (Membership.GetUser() == null)
            Server.Transfer("Login.aspx");
        userID = (Guid)Membership.GetUser().ProviderUserKey;
        if (userID == null)
            Server.Transfer("Login.aspx");

Confirm you've removed any Login control instructions for where to re-direct the user after authentication and now you should see your application behave appropriately by redirecting the user back to their originally intended destination following authentication. 

My problem was that I was not taking full advantage of the Membership features and allowing the application to lock the user out automatically.  In doing so, and manually re-directing the user to the Login.aspx page, the application had no idea where my user had originally intended to go.

I hope my ignorance and frustration helps someone else out along the way.