G
Guest
One thing I did a lot of in Classic ASP involved showing page elements
conditionally based on whether a user was logged in or not. Logged in users
or "superusers" would get more content and/or more controls if my pages
detected their login. Non-logged in users would also get some page content
at a given URL, but the protected content was hidden from them.
I would like to know generally how this is done in ASP.NET. I'm particularly
interested in understanding how you make this happen within the froms
authentication/authorization framework that's built into ASP.NET 1.1 or 2.0.
Lots of tutorials online show me how to boot people off page and back to
login if they aren't logged in. This isn't what I want. I'd like to show
non-logged in folks a minimal version of the page, and show logged-in folks
a lot more.
Pretty sure this is a simple thing involving a session variable or somesuch.
Can someone point the way to the best practice?
-KF
conditionally based on whether a user was logged in or not. Logged in users
or "superusers" would get more content and/or more controls if my pages
detected their login. Non-logged in users would also get some page content
at a given URL, but the protected content was hidden from them.
I would like to know generally how this is done in ASP.NET. I'm particularly
interested in understanding how you make this happen within the froms
authentication/authorization framework that's built into ASP.NET 1.1 or 2.0.
Lots of tutorials online show me how to boot people off page and back to
login if they aren't logged in. This isn't what I want. I'd like to show
non-logged in folks a minimal version of the page, and show logged-in folks
a lot more.
Pretty sure this is a simple thing involving a session variable or somesuch.
Can someone point the way to the best practice?
-KF