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 FormsAuthentica tionTicket cookies seem to overwrite each other.

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

[Paul Shapiro]

Re: Two websites, same FormsAuthentica tionTicket?

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

"Jeff Dege" <jdege@jdege.vi si.comwrote in message
news:13s8mvgnje 70e64@corp.supe rnews.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 FormsAuthentica tionTicket cookies seem to overwrite each other.

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

RE: Two websites, same FormsAuthentica tionTicket?

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="VirtualDi rectoryAlias" ... />

--
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 FormsAuthentica tionTicket cookies seem to overwrite each other.
>
--
When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl.
>