Do you mean you don't just dont want to use the inbuilt 'asp.net login control'?
If so, you still need some sort of way of taking some credentials from the user and validating them so the user is logged in & issuing them a token. Otherwise, how will you tell if the user is logged in or not?
You can create your own login control logic - I suggest you still use the Membership provider for this but you can override & do what you like here.
http://msdn.microsoft.com/en-us/library/yh26yfzy.aspx[
^]
Most websites that require you to sign in have a 'log out' link that will invalidate their token and redirect them back to some resource that doesn't require authentication (e.g. your 'Home' page). I also suggest you go this way rather than trying to mess with the 'back' button.
Correctly issuing an authentication token + use of page cache directives won't allow the user to click on the 'back' button to view any pages that require authentication.
Submit an article or tip