Problem navigating to subwebs

[Daveyman]

Hi,

I'm having a problem navigating to/from a subweb using forms authentication.

The setup in IIS is as follows:
TestSite
+----SecureDir
+----ReportsSubWeb

In VS.Net 2003 this has been set up as a single solution containing two
projects; the first project contains TestSite and SecureDir, and the second
project contains ReportsSubWeb as a subweb of TestSite. ReportsSubWeb is
referenced by TestSite.

Where 'TestSite' contains various screens (i.e. welcome/logon, etc),
'SecureDir' is a folder within website and contains 'secure' functionality,
and 'ReportsSubWeb' is a IIS subweb below the TestSite. The reason I'm
wanting to do Reports as a seperate subweb is because the .dll will contain
several entry points for new reports which are to be added in the future;
I'd like to be able to distribute the .dll alone without having to recompile
to webapp each time. Forms authentication is used throughout, and only
authenticated users must be able to access SecureDir and ReportsSubWeb.

Currently, I'm able to navigate directly to SecureDir from both TestSite and
ReportsSubWeb, however once in ReportsSubWeb navigating to SecureDir throws
me back to the signon screen, as does attempting to navigate to any page
within the ReportsSubWeb. Although session variables and the security cookie
appear to work and be passed through to the first form on the ReportsSubWeb
they have no further effect.

In a nutshell, what I really need to know is (1) is this possible?, and (2)
if so, how?

Any help appreciated!

Cheers, D.

 

[Steven Cheng[MSFT]]

Hi Daveyman,

From your description, you've host two asp.net webapplications in your IIS
server and one is nested in another(in the subfolder of the upper app)
which contains some separate dlls. Also, you want the two web applications
share a common FormsAuthentication setting to secure the files/folders in
both web app and meet problem on this,yes?

Since you mentioned that
=============================================
The reason I'm
wanting to do Reports as a seperate subweb is because the .dll will contain
several entry points for new reports which are to be added in the future;
I'd like to be able to distribute the .dll alone without having to recompile
to webapp each time.
=============================================

Could the "several entry points" dll be developed as a certain class
library( a single dll) so that we can put it in the main project's bin
folder and not use two web applications.
If we do have to use two web application( parent and nest one), then we
have to do some configurations for the FormsAuthentication if we want the
two different asp.net web application to share the same formsauthentication
token at runtime, below is the related reference in msdn:

#Forms Authentication Across Applications
http://msdn.microsoft.com/library/en-us/cpguide/html/cpconformsauthenticatio
nacrossapplications.asp?frame=true

Please have a look to see whether it helps. Thanks.

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

 

[Daveyman]

Thanks Steven, I'll have a look.