By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,058 Members | 1,217 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,058 IT Pros & Developers. It's quick & easy.

Maintaining Authentication across ASP.Net Web Apps

P: n/a
Os
Hi,

What would be a good way to maintain authentication across web
applications?

I have an existing application (Framework 1.1) which does the user
authentication. Currently, we have developed another application in
Framework 2.0 which will only allow authenticated users from the
Framework 1.1 application to view the information.

Can anyone advise how I can achieve this?

Thank you!

Dec 6 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Basically cookies will allow you to handle this type of authentication as
long as the domains are the same.

http://www.mydomain.com/WebApp11
and
http://www.mydomain.com/WebApp20

If you setup a cookie and the path is / then you could read the cookie from
either application.

--

Cheers

Chris Crowe [IIS MVP 1997 -> 2006]
http://blog.crowe.co.nz
------------------------------------------------
"Os" <os****@gmail.com> wrote in message
news:11*********************@z14g2000cwz.googlegro ups.com...
Hi,

What would be a good way to maintain authentication across web
applications?

I have an existing application (Framework 1.1) which does the user
authentication. Currently, we have developed another application in
Framework 2.0 which will only allow authenticated users from the
Framework 1.1 application to view the information.

Can anyone advise how I can achieve this?

Thank you!

Dec 6 '05 #2

P: n/a
Os
Hi Chris,

Thanks for the reply.

When using cookies, will there be any security issues?
How can I ensure and convince others that the cookie cannot be
replicated to authenticate another user?

Dec 6 '05 #3

P: n/a
hi,
There are different way to handle authentication with cookies.
The most secure is to store in the cookie, a crypted user id.
Then that user ide will be store in a databse USER ACCESS table in which you
will have user authentication information based on the crypted ID read from
the cookie

serge
MCP (XP, VB.NET,ASP.NET)

"Os" wrote:
Hi Chris,

Thanks for the reply.

When using cookies, will there be any security issues?
How can I ensure and convince others that the cookie cannot be
replicated to authenticate another user?

Dec 6 '05 #4

P: n/a
Os
Thanks Chris and Serge!

I think i have a basic idea of how it is now.

Much appreciated!

Dec 6 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.