Home

EDGE issues within WVD

%3CLINGO-SUB%20id%3D%22lingo-sub-1222529%22%20slang%3D%22en-US%22%3EEDGE%20issues%20within%20WVD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1222529%22%20slang%3D%22en-US%22%3E%3CP%3EPilot%20users%20are%20having%20an%20issue%20with%20the%20EDGE%20browser%20within%20WVD%2C%20when%20accessing%20sites%20that%20leverage%20ADFS.%20Users%20can%20connect%20to%20one%20host%2C%20one%20day%20and%20Edge%20will%20work%20as%20expected%20when%20accessing%20sites.%20The%20next%20day%20they%20may%20connect%20to%20a%20different%20host%20and%20the%20will%20receive%20an%20error%20when%20trying%20access%20sites%20that%20leverage%20ADFS.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20error%20generated%20is%20%22Cannot%20connect%20securely%20to%20this%20page%22%20%22This%20might%20be%20because%20the%20site%20uses%20outdated%20or%20unsafe%20TLS%20security%20settings.%20If%20this%20keeps%20happening%20try%20contact%20the%20website%20owner.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20the%20users%20opens%20up%20IE%20in%20the%20same%20session%2C%20they%20can%20access%20the%20site%2C%20if%20the%20user%20resets%20edge%20via%20settings%2Fapps%20the%20site%20starts%20working%20(until%20they%20move%20to%20a%20different%20host%2C%20it%20appears%20again)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20implemented%20Redirections.xml%2C%20but%20are%20currently%20only%20excluding%20(%3CEXCLUDE%20copy%3D%22%26quot%3B0%26quot%3B%22%3EAppData%5CLocal%5CPackages%5CMicrosoft.MicrosoftEdge_8wekyb3d8bbwe%5CAC%5CMicrosoftEdge%5CCache%3C%2FEXCLUDE%3E)%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Pilot users are having an issue with the EDGE browser within WVD, when accessing sites that leverage ADFS. Users can connect to one host, one day and Edge will work as expected when accessing sites. The next day they may connect to a different host and the will receive an error when trying access sites that leverage ADFS. 

 

The error generated is "Cannot connect securely to this page" "This might be because the site uses outdated or unsafe TLS security settings. If this keeps happening try contact the website owner."

 

If the users opens up IE in the same session, they can access the site, if the user resets edge via settings/apps the site starts working (until they move to a different host, it appears again)

 

We have implemented Redirections.xml, but are currently only excluding (<Exclude Copy="0">AppData\Local\Packages\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\AC\MicrosoftEdge\Cache</Exclude>)