Basically this needs to be done so that:

a) synchronize <machineKey> elements in web.config for all applications
b) synchronize <authentication> elements in web.config and ensure apps use
same set of credentials

a) Means creating explicit and same values for machineKey attributes on both
apps
b) means that for example authentication cookie name needs to be exactly the
same and so on.

Hope this gives you a start. You might also want to check following
document:

Building Secure ASP.NET Applications: Authentication, Authorization, and
Secure Communication:
[url]http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/secnetlpMSDN.asp[/url]

--
Teemu Keiski
MCP, Designer/Developer
Mansoft tietotekniikka Oy
[url]http://www.mansoft.fi[/url]

ASP.NET Forums Moderator, [url]www.asp.net[/url]
AspAlliance Columnist, [url]www.aspalliance.com[/url]

Email:
[email]joteke@aspalliance.com[/email]
"Russ" <russ@acordiamn.com> wrote in message
news:O8$voF$PDHA.1608@TK2MSFTNGP11.phx.gbl...
> I have a project that I created a couple months ago that uses forms
> authentication with a couple usernames and passwrods stored in the
> web.config file. I am now working on a new project that will be installed
> on the same webserver that I would like to use the same authentication.
> What I mean is if a person clicks on a link in my old project that leads
to
> the new one they will not need to log in again. Is this difficult to do?
>
>