D
darrel
A couple of us are working on some admin tools for our site. For a variety
of reasons (some good, some arbitrary, either way, it's what we're doing...)
we decided to use a couple independant applications and tie them together
with a simple HTML template. So, right now, we have 3 individual .net
applications that 'look and feel' like one to the end user.
The one catch is that we're using forms authentication, which requires (from
what I can tell) a unique cookie for each application. This means as the
user is using the site, they may have to log in a number of times.
Is there a way to handle 3 separate applications with one authentication
system? One option that I came up with is that instead of writing a cookie,
write to a table on the server. We weren't quite sure how to handle timing a
log-in out, though. Is that a valid option?
-Darrel
of reasons (some good, some arbitrary, either way, it's what we're doing...)
we decided to use a couple independant applications and tie them together
with a simple HTML template. So, right now, we have 3 individual .net
applications that 'look and feel' like one to the end user.
The one catch is that we're using forms authentication, which requires (from
what I can tell) a unique cookie for each application. This means as the
user is using the site, they may have to log in a number of times.
Is there a way to handle 3 separate applications with one authentication
system? One option that I came up with is that instead of writing a cookie,
write to a table on the server. We weren't quite sure how to handle timing a
log-in out, though. Is that a valid option?
-Darrel