Two websites, same FormsAuthenticationTicket?

[Jeff Dege]

We have two different websites, both written in ASP.NET 2.0/C#, running
in different virtual directories on the same server.

They both use forms authentication.

Their FormsAuthenticationTicket cookies seem to overwrite each other.

--
When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl.

[Paul Shapiro]

In the respective application root's web.config add a unique setting for the
authentication name property:
<authentication mode="Forms">
<forms
name="MyApplication.ASPXAUTH"
path="/"
loginUrl="~/Login.aspx"
... etc.

"Jeff Dege" <jd***@jdege.visi.comwrote in message
news:13*************@corp.supernews.com...

We have two different websites, both written in ASP.NET 2.0/C#, running
in different virtual directories on the same server.

They both use forms authentication.

Their FormsAuthenticationTicket cookies seem to overwrite each other.

[=?Utf-8?B?UGF1bHVzIEUgS3Vybmlhd2Fu?=]

Jeff,

Configure the authentication section in your web.config file to use a unique
name for the authentication cookie. The virtual directory name/alias is a
good choice.

<forms name="VirtualDirectoryAlias" ... />

--
Paulus E Kurniawan
http://www.paulusevan.net
"Jeff Dege" wrote:

We have two different websites, both written in ASP.NET 2.0/C#, running
in different virtual directories on the same server.

They both use forms authentication.

Their FormsAuthenticationTicket cookies seem to overwrite each other.

--
When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl.