Hey everyone,
I have several web applications running on various domains and they all point to a single database connected app on another domain.
For this example we'll say the web application is on domain1.com. The home page for domain1.com opens a login window in an IFRAME. That login window points to the database connected application on a secure server. Let's call that one domain2.com.
So in this IFRAME the user logs in on domain2.com, and my ASP page processes the credentials and sets a login cookie using Response.Cookies.
Then it redirects to the menu page on domain2.com using window.top.location.href so that the domain2 application now takes up the whole window. However when it gets to the menu page it does not find the cookie.
I tried it also using a Session var and the same thing happens. When I call the window.top.location.href does that essentially start a new session?
-Greg
I have several web applications running on various domains and they all point to a single database connected app on another domain.
For this example we'll say the web application is on domain1.com. The home page for domain1.com opens a login window in an IFRAME. That login window points to the database connected application on a secure server. Let's call that one domain2.com.
So in this IFRAME the user logs in on domain2.com, and my ASP page processes the credentials and sets a login cookie using Response.Cookies.
Then it redirects to the menu page on domain2.com using window.top.location.href so that the domain2 application now takes up the whole window. However when it gets to the menu page it does not find the cookie.
I tried it also using a Session var and the same thing happens. When I call the window.top.location.href does that essentially start a new session?
-Greg