With the old C# client, when a user installed our plugin on a system that didn't have a signed certificate, they were able to allow for the bad/lack of SSL certificate and continue to the page. This certificate acceptance was possible since the C# client used an embedded IE.
With the new Web Client environment, when using the HTML bridge we direct the display to a page served by our plugin's server that isn't installed on a system with a certificate, there is no opportunity/option for the user to accept the lack of certificate. Instead the display area just shows the little unhappy face icon in the center.
I have been trying to come up with a solution (besides the obvious of having the customer install a proper certificate on their system) to let the customer know they don't have a certificate and allow them to accept the server/page (perhaps by having them point their browser to a page I would supply from my server that they could then accept the certificate/exception for).
↧
HTML Bridge webpage display for invalid SSL certificate
↧