When the session storage is cleared, this state is lost and hence results in broken experiences. MSAL.js saves certain state in the session storage and relies on checking this state during the authentication flows. Specifically, the session storage is cleared in the regular browser navigation, and both the session and local storage are cleared in the InPrivate mode of the browser. In this particular version of Microsoft Edge, when the application is redirected across zones, the session storage and local storage are cleared. The session storage and local storage are partitioned by security zones in the Microsoft Edge browser. The cause for most of these issues is as follows. While Microsoft Edge works on a resolution, here is a description of the frequently occurring issues and the possible workarounds that can be implemented. We are tracking these and have informed the Microsoft Edge team. We had multiple reports of issues with authentication in IE and Microsoft Edge (since the update of the Microsoft Edge browser version to 40.15063.0.0). Kindly help and identify where i did mistake.Feedback In this article Issues due to security zones I am unable to login through Edge server. If you are using automatic configuration, the network administrator will need to double-check the DNS A record configuration for because it could not be resolved. If you are using manual configuration for Communicator, please check that the server name is typed correctly and in full. The test OCS connectivity site shows the below error when I have tried to sign in,Īlso at client side the below error occurĬommunicator was unable to resolve the DNS hostname of the login server.
The edge external and internal certificates issued by DigiCert and have below SAN address Port 443 and _sipfederationtls._ on port 5061 target to edge server
On Public DNS, “A” records “” points to “111.XX.XX.Public”.
External Access and Access Edge configuration are set as belowīoth FE and Edge can ping each other through FQDN IP.
0 kommentar(er)
