Bug 5997 - Infinite loading animation with untrusted certificates doesn't work on Edge
Summary: Infinite loading animation with untrusted certificates doesn't work on Edge
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Web Access (show other bugs)
Version: pre-1.0
Hardware: PC Unknown
: P2 Normal
Target Milestone: MediumPrio
Assignee: Samuel Mannehed
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-20 16:15 CEST by Samuel Mannehed
Modified: 2019-10-31 11:12 CET (History)
2 users (show)

See Also:
Acceptance Criteria:


Attachments

Description Samuel Mannehed cendio 2016-09-20 16:15:00 CEST
Seen on Edge version 25.

Steps to reproduce: 
1. surf to castro.lkpg.cendio.se:300 and accept the unsigned certificate
2. log in
3. you are now redirected to the agent tl.cendio.se (which in this example is on the same machine) but Edge doesn't display the dialogue for accepting the unsigned certificate. - You are stuck on the "redirecting.." screen.


On non-cluster setups of ThinLinc you can work around this by directly surfing to the same hostname that is specified in agent_hostname.
In cluster setups this won't work out, since the master isn't running on the agent machines. You will have to get a signed certificate.

OR:

You can upgrade to a newer version of Microsoft Edge. Version 38 of Edge does show the certificate dialogue even for the agent.
Comment 1 Karl Mikaelsson cendio 2016-09-21 11:15:28 CEST
(In reply to comment #0)
> You can upgrade to a newer version of Microsoft Edge. Version 38 of Edge does
> show the certificate dialogue even for the agent.

Nope - it's still broken with Edge 38.14393.0.0.
Comment 2 Samuel Mannehed cendio 2019-10-16 15:29:33 CEST
Since the latest vendordrop of noVNC (for thinlinc 4.11.0) we no longer have the "redirecting.."-screen, we now instead have a loading animation.

So this bug will result in an infinite loading animation.
Comment 3 Niko Lehto cendio 2019-10-22 14:07:30 CEST
For some reason, these problems disappears if you open developer console and reload the page.

Note You need to log in before you can comment on or make changes to this bug.