Login / Signup

Is WebVue (12.0.0-dev [29820]) incompatible with Microsoft Edge?

 
WebVue
Last Post by b.lepeuple 7 years ago
2 Posts
2 Users
0 Likes
34 Views
RSS
 AT
(@a-tanarcinfo-com)
Posts: 15
Eminent Member
Topic starter
 

Hi,

I would like to ask if there is an incompatibility between WebVue and Microsoft Edge? An error message appears when a user would try to log in.
Has anyone encountered this issue as well?

Thanks.

4568=711-2edb844f0459d508ef3ba88faf6d595e
 
Posted : 07/11/2019 9:34 am
b.lepeuple
 b.lepeuple
(@b-lepeuplearcinfo-com)
Posts: 149
Estimable Member
 

Hi, If I am not mistaken, you fall on one of the well-known issue with MS Edge. From the online help: Restrictions related to web browsers Each web browser can come with its own restrictions, in particular when security is at stake. Below is a list of known behaviors, specific to one or the other web browser available on the market at the time of writing. These restrictions may be cleared and others appear depending on web browser updates and their publisher's strategy.

  • Safari on iOS - When the Safari web browser is closed without logging out from WebVue, WebVue is re-open by default the next time the user opens Safari, but the user will not be able to successfully login, and will be stuck on the WebVue loading page. This is due to the Safari snapshot of the last visited page where Safari display the web page without actually requesting the web server. The solution is to go to the address bar and click the Go button, or ask Safari to reload the page.
  • Google Chrome - The password manager of Chrome does not store credentials if the connection to the web server is insecure. As a consequence, if you do not have a proper certificate on the web server, users will not be able to use the Chrome password manager to store their credentials.
  • Microsoft Edge - Edge does not store the session cookie when using the local computer as a web server with a binding on the hostname at the IIS level. As a consequence, you cannot successfully log in, and can see a warning message indicating that the version of the client is not compatible with the server. The solution is to add .local to the computer host name when setting up the web site binding with the Web Deployment Console (for example, "https://mycomputername.local" instead of "https://mycomputername").
This post was modified 2 years ago by LM
 
Posted : 07/11/2019 2:21 pm
Forum Jump:
Next Topic