Cookie loss problem (authentication failure) Authentication (user verification information) will also be lost_javascript skills

I wonder if you have ever encountered such embarrassment:

When your page authentication uses a cookie-based method, such as form, windows integrated authentication, sometimes the authentication will fail after the following operations, and the Authentication (user verification information) will be lost, and you need to log in again
After the system logs in normally:

The first page (PageA.htm): After window.showModalDialog(), the second page (PageB.htm) pops up

The second page (PageB.htm): After window.open(), the pop-up window (PageC.htm) sometimes jumps to the login page

This should be due to different pages existing in different processes, resulting in identity information being out of sync and authentication failure occurring. However, this happens with a certain probability. With the help of MS consultants, I finally found a method:
In summary, when showModalDialog(), pass window as the object parameter to PageB.htm. In PageB, use this parameter to open(), so the problem is solved
The details are as follows:
-- ----------PageA.htm-------------
...
var obj = new Object();
obj.myTestWindowA = window;//Save this window into the object parameter
window.showModalDialog("PageB.htm",obj,"");
...
---------- --------------------------

----------PageB.htm-------------
...
var obj = window.dialogArguments;//Get Parameters of the previous page
obj.myTestWindowA.open("PageC.htm");//Use the parameters passed from the previous page to open the next page
...
------ ----------------------------
After testing, there is no more identity loss, and you're done!
Careful friends will find that such an operation will cause that in PageC.htm, since the opener is not PageB.htm but PageA.htm, window.opener cannot be used to communicate with PageB.htm, and open() I can't pass object parameters again, panic!
Fortunately, in JavaScript, the object is a big tree, and you can hang anything on its branches. Therefore, in order for PageC.htm to communicate with PageB.htm, we modified PageB.htm as follows:
-----------PageB.htm--------------
...
var obj = window.dialogArguments;//Get the previous Parameters of the page
var obj.myTestWindowA.myTestWindowB = new Object();
obj.myTestWindowA.myTestWindowB = window; //Hang PageB’s window under the window branch of PageA
obj.myTestWindowA. open("PageC.htm");//Open the next page using the parameters passed from the previous page
...
------------------ ----------------
In this way, you can communicate with the object of the PageB page through window.opener.myTestWindowB in PageC, such as window.opener.myTestWindowB.document. getElementById("TextBox1").value="OK"

Note:
1. This may be just a situation. Opening first and then showing ModalDialog may also cause the loss of identity information, but as long as you pass the window with no problem to the next page, the problem can be solved.

(Please refer to http://www.ourac.net/read.php?tid=45123&fpage=2)
2. It may also be in Session occurs, see http://support.microsoft.com/default.aspx?scid=kb;EN-US;196383