Hi,
We have a web application which does the below steps:
1. Load Okta login widget on our web page (widget is hosted from a different domain)
2. Perform form based on authentication provided by Okta widget. The server after successful authentication responds with a set-cookie
3. Upon "clicking" on a specific button, navigate to a specific page in Okta (clicking on the button runs a window.location = "some okta page" JS command). At this point the navigation is expected to carry the cookies set in previous step.
on build 16299, when window.location is used, I see that the operation is spinning up a new IE process (process number identified from Fiddler) on windows and also the cookies are not being attached when navigating to the specific page in Okta.
(Not sure if older builds of Windows 10 are having a problem, build 17134 does NOT have this problem. Behavior also NOT observed with Windows 7 builds and web page also works fine with Chrome in all the Windows flavors).
While the problem certainly seems to be fixed with the latest build, we need to know on what the problem is so that we can warrant for a enterprise wide push for the latest update from Windows.
Thanks,
Rakesh Panati
