In my application, I have a page that loads from https://hostname:8443 which loads an iframe with the host/ip combination of the openfire server hostname and the http-bind ssl port (7443) to load a library that establishes a BOSH connection with Openfire.
The problem is that the openfire server has a self-signed certificate which the client browser cannot “accept” or “trust” since it’s loaded in an iframe within the page. The current workaround is to access the https://hostname:7443 resource that is loaded up by the iframe and accept that certificate in the browser and then going back to access the https://hostname:8443 page.
Has anyone encountered this issue and/or know of a way around it?