A
Author
1. We have two different asp.net websites (created as website projects
instead of web application projects).
2. We need to provide single login and logout for both websites. In
other words, a user logs in, clicks on Site A, s/he should be able to
access Site A, if s/he clicks on Site B, s/he should be able to access
Site B. If the user logs out, s/he should logout both websites.
Site A has these navigation menus:
Home | Menu1 | Menu2 | Menu3 | Site B | Logout
Site B has these navigation menus:
Home | Menu1 | Menu2 | Menu3 | Site A | Logout
What is the best solution such that when a user logs in, both
applications are aware of this authenticated user, and when s/he logs
out, s/he is logged out of both?
I am thinking of storing the session id, user name in a sql server
database, and pass the session id to either site in a query string.
Will this work? What problem should I anticipate?
Anyone did this before?
instead of web application projects).
2. We need to provide single login and logout for both websites. In
other words, a user logs in, clicks on Site A, s/he should be able to
access Site A, if s/he clicks on Site B, s/he should be able to access
Site B. If the user logs out, s/he should logout both websites.
Site A has these navigation menus:
Home | Menu1 | Menu2 | Menu3 | Site B | Logout
Site B has these navigation menus:
Home | Menu1 | Menu2 | Menu3 | Site A | Logout
What is the best solution such that when a user logs in, both
applications are aware of this authenticated user, and when s/he logs
out, s/he is logged out of both?
I am thinking of storing the session id, user name in a sql server
database, and pass the session id to either site in a query string.
Will this work? What problem should I anticipate?
Anyone did this before?