Secure some pages and not other

[Shimon Sim]

I am creating application that is mostly is used by registered user. I am
using Form security to let user in. I also need to create registration for
users. This of cause has to be accessible to everyone.
Can I do everything in one ASP.NET application or I have to create two
applications for each task?
Thanks,
Shimon.

[Beginner]

Put all secured page in one directory and use a seperate web.config in that
direcotry to specify <authorization> <deny ...>

"Shimon Sim" <es*****@att.ne t> wrote in message
news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..

I am creating application that is mostly is used by registered user. I am
using Form security to let user in. I also need to create registration for
users. This of cause has to be accessible to everyone.
Can I do everything in one ASP.NET application or I have to create two
applications for each task?
Thanks,
Shimon.

[Steven Cheng[MSFT]]

Hi Shimon,

Thanks for posting in the community!
From your description, you're using the Formsauthentica tion in your ASP.NET
web app. And you've some different sets fo files in your web apps which are
protected from different groups of users(protected level). So you're
wanting how to set such multi-authroized configuration in a single ASP.NET
web app, yes?
If there is anything I misunderstood, please feel free to let me know.

Based on my experience, you may have a try on the <location> Element in the
web.config file. This element can help apply a certain sections of
configuration to a certain specified part of a web app(via url path). Here
are the referernce of the <location> Element in MSDN:

#<location> Element
http://msdn.microsoft.com/library/en...ationelement.a
sp?frame=true

As for your situation , you can put those different protected files into
several sub dirctories in the web app's root folder. Then use the
<location> Element to specify different authorization settings for these
sub directories. For example:
If we have a web app named MyApp(used formsauthentica tion) and has the
following folder hierarchy:
MyApp/
....public resources
Admin/
....admin protected level resources
User/
....normal user protected level resources

Then we can specify different authorization protections for them via t he
below configuration in web.config
<configuratio n>
<system.web>
<authenticati on mode="Forms">
<forms name=".ASPNET_F ORM_NAME" loginUrl="login .aspx" >
</forms>
</authentication>

<authorizatio n>
<allow users="*" />
</authorization>
</system.web>

<!¡ª Configuration for the "Sub1" subdirectory. -->
<location path="Admin">
<system.web>
<authorizatio n>
..... Authrozation for Admin
</authorization>
</system.web>
</location>

<!¡ª Configuration for the "Sub2" subdirectory. -->
<location path="sub2">
<system.web>
<authorizatio n>
..... Authrozation for Normal user

</authorization>
</system.web>
</location>
</configuration>

In addition, here are some further tech references on how to apply
heirarchical configuration Inheritance in web.config:

#Configuration Inheritance
http://msdn.microsoft.com/library/en...igurationinher
itance.asp?fram e=true

#Configuration <location> Settings
http://msdn.microsoft.com/library/en...igurationlocat
ionsettings.asp ?frame=true

#Locking Configuration Settings
http://msdn.microsoft.com/library/en...ingconfigurati
onsettings.asp? frame=true

Please refer to them if you feel anything unclear.
Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx