This is related to the concept of sign-on (SSO).You can do it easily if you are using asp.net 2.0/3.5/4.0
Cookied Cross-Application Behavior
You can use diff applications to the cookieless sample to also show cross-application redirects in
the cookied case. Again using two sample applications (App1 A and AppB), both applications need to share a common
configuration:
<forms cookieless="UseCookies" enableCrossAppRedirects="true"
path="/cookiedAppA"/>
<machineKey
decryptionKey="A225194E99BCCB0F6B92BC9D82F12C2907BD07CF069BC8B4"
validationKey="6FA5B7DB89076816248243B8FD7336CCA360DAF8"
/>
To simulate isolation of the forms authentication cookies, each application explicitly sets the path attribute
as shown above.
Because this sample uses cookies, the path attribute prevents the browser from
sending the forms authentication cookie for one application over to the second application. Remember
that setting the path attribute only takes effect when using cookied modes (for example, setting the path
attribute would have no effect on the previous cookieless example). For now, we will use the same
redirection helper as we did earlier, and pages in both applications will issue a Response.Redirect to
get to the second application.
//First application button click
FormsAuthentication.RedirectFromLoginPage("testuser", false);
Response.Redirect("/cookielessAppB/default.aspx");
-Hope this works.cheers!
Kishor Kumar
kishor kumar
Shubhashree, if this helps please login to Mark As Answer. | Alert Moderator