aspx_professional thread: using different authentication modes in the same application
I didn't mean that Forms Auth was limiting, sorry. I meant that if you
are limiting the architecture to using JUST Forms Auth, as opposed to
having a hybrid mix. That's all. Such as a custom security model rolled
in, or something.
-----Original Message-----
From: Nick Charlesworth [mailto:nick@f...]
Sent: Friday, August 09, 2002 11:50 AM
To: ASPX_Professional
Subject: [aspx_professional] RE: using different authentication modes in
the same application
Why do you think forms authentication is 'Limiting'.
Do you think it better to use a session variable to hold the userID
after
a successful login and then check for this variable at the top of each
page?
> That is the correct way to approach it, if you are limiting yourself
> to
forms authentication. In some of my web apps, I plan on this when I do a
site map and information architecture by encoding the access level in
the page number. P for public pages, and they go in a sub folder called
public. M for member, and A for admin. I also usually have a global
resources folder with sub folders for images broken out by use, but each
P/M/A folder will also have its own local resource folder.=3D20
Brian Prince
-----Original Message-----
From: Nick Charlesworth [mailto:nick@f...]=3D20
Sent: Friday, August 09, 2002 10:13 AM
To: ASPX_Professional
Subject: [aspx_professional] using different authentication modes in the
same application
Hi,
Is it possible to use different authentication modes in the same=3D20
application.
i.e. A site that contains a shopping cart might want it's initial
home=3D20 page and contact us page to require no authentication but it's
shopping=3D20 cart checkout pages might require forms authentication.
If I enable forms authentication this means that all aspx files will=3D20
require a forms login before they can be accessed.
I do not want to make the home page .htm or .html as it must carry
out=3D20 other asp.net functionality.
Is the correct solution to allow anonymous access in the root
directory=3D20 and then place all pages requiring authentication in a sub
folder with=3D20 it's own web.config file that requires forms
authentication?
If this works will application and session variables be carried
through=3D20 from non-authenticated pages to authenticated pages and
vice-versa?
thanks,
Nick
---
ASP.NET 1.0 Namespace Reference with C#
http://www.wrox.com/acon11.asp?ISBN=3D3D1861007442
ASP.NET 1.0 Namespace Reference with VB.NET
http://www.wrox.com/acon11.asp?ISBN=3D3D1861007450
These books are a complete reference to the ASP.NET namespaces=3D20 for
developers who are already familiar with using ASP.NET.=3D20 There is no
trivial introductory material or useless .NET=3D20 hype and the
presentation of the namespaces, in an easy-to use=3D20 alphabetical order
ensures a user-friendly reference format. We provide in-depth coverage
of all the major ASP.NET classes,=3D20 giving you those real-world tips
that the documentation doesn't=3D20 offer, and demonstrating complex
techniques with simple=3D20 examples. =3D20
---
---
Change your mail options at http://p2p.wrox.com/manager.asp or=3D20 to
unsubscribe send a blank email to
<FONT face=3D3DArial size=3D3D1>
************************************************************************
***
=3D
****************************************
This message (including any attachments) contains confidential
information
=3D
intended for a specific=3D20
individual and purpose, and is protected by law. If you are not the
intend=3D
ed recipient, you should
delete this message. Any disclosure, copying, or distribution of this
mess=3D
age, or the taking of any=3D20
action based on it, is strictly prohibited.
************************************************************************
***
=3D
****************************************
</FONT>
---
ASP.NET 1.0 Namespace Reference with C#
http://www.wrox.com/acon11.asp?ISBN=3D1861007442
ASP.NET 1.0 Namespace Reference with VB.NET
http://www.wrox.com/acon11.asp?ISBN=3D1861007450
These books are a complete reference to the ASP.NET namespaces
for developers who are already familiar with using ASP.NET.
There is no trivial introductory material or useless .NET
hype and the presentation of the namespaces, in an easy-to use
alphabetical order ensures a user-friendly reference format.
We provide in-depth coverage of all the major ASP.NET classes,
giving you those real-world tips that the documentation doesn't
offer, and demonstrating complex techniques with simple
examples.
---
<FONT face=3DArial size=3D1>
***************************************************************************
****************************************
This message (including any attachments) contains confidential information
intended for a specific
individual and purpose, and is protected by law. If you are not the intend
ed recipient, you should
delete this message. Any disclosure, copying, or distribution of this mess
age, or the taking of any
action based on it, is strictly prohibited.
***************************************************************************
****************************************
</FONT>