Forms-Based Authentication for only a subset of pages

[Guest]

I've got the basic forms based authentication going. A user has to go to my
login page before they can access any other pages. The issue is that there
are a sub-set of pages on which I don't have to require that a user login in
before they access it (the contact/about page for example). I've tried
copying all my 'secure' pages to a sub-directory of my application and then
set up the web.config in this sub-dir to use forms, leaving the web.config in
the main dir as non-form based authentication. but this didn't seem to work.
Even after logging in, I'd still get re-directed back to the login page every
time I accessed a page in the secure sub-dir.

What's the usual strategy for setting up this type of configuration?

Thanks for the help.

 

[John Saunders]

I've got the basic forms based authentication going. A user has to go to
my
login page before they can access any other pages. The issue is that
there
are a sub-set of pages on which I don't have to require that a user login
in
before they access it (the contact/about page for example). I've tried
copying all my 'secure' pages to a sub-directory of my application and
then
set up the web.config in this sub-dir to use forms, leaving the web.config
in
the main dir as non-form based authentication. but this didn't seem to
work.
Even after logging in, I'd still get re-directed back to the login page
every
time I accessed a page in the secure sub-dir.

Does this happen when you have all the pages in one directory? This is not
the behavior that I would expect.

What's the usual strategy for setting up this type of configuration?

I usually set up a single web.config, in the root of the application. I put
the unsecured pages in a few subdirectories, for instance login/, public/
and help/. I then use <location> elements in the web.config to specify that
anyone can access the pages in those subdirectories.

John Saunders

 

[Guest]

I usually set up a single web.config, in the root of the application. I put
the unsecured pages in a few subdirectories, for instance login/, public/
and help/. I then use <location> elements in the web.config to specify that
anyone can access the pages in those subdirectories.

John Saunders

Thanks for the help John. I suspected there must be something like
<location> but I didn't find it in the help. Once I set up the <location>,
as per your suggestions, everything worked great.

Andre.