Detect ssl warning message
I work for a company that ships data storage appliances with a GUI web application and several rest API services that the GUI web app talks to through SSL. Because each customer has a different domain, the SSL warning comes up in the browser. So the customer has to hit each rest API service first, click OK for the SSL warning, and only then will the entire application work. My question is if there is some way to facilitate this process where if the customer hits the front end web app first, we can detect that the warning is occurring with the rest API services and maybe bring up a separate window to allow the user to click OK for the warning.
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
We are already using a self-signed certificate and you're correct about the warning only coming up once (unless the browser data is cleared), but that is the situation I'm trying to more elegantly handle.
This is by design - its what the certs are *supposed* to do.
In order for no alert to come up, the cert must meet the following:
a) the name must be correct (i.e. what the user typed into the browser must be what the certificate contains)
b) the date range must be correct (i.e. the certificate must have a start time in the past and an end time in the future)
c) the certificate must be signed by a CA the browser trusts.
of the three, the latter is usually the hardest. Its easy for a server to self-generate and self-sign the certificate to meet a), and specifying "now until ten years from now" usually takes care of b), leaving only c) to deal with. In a modern MS environment though, you can usually expect that there is a corporate CA available, so that means arranging for your appliance to request a certificate from such a CA rather than generating internally. This should be part of setup - so after getting a dns name and ip, display a CSR and request it be signed, offering - as the alternative - to import a pfx file and/or self-generate a cert.
In order for no alert to come up, the cert must meet the following:
a) the name must be correct (i.e. what the user typed into the browser must be what the certificate contains)
b) the date range must be correct (i.e. the certificate must have a start time in the past and an end time in the future)
c) the certificate must be signed by a CA the browser trusts.
of the three, the latter is usually the hardest. Its easy for a server to self-generate and self-sign the certificate to meet a), and specifying "now until ten years from now" usually takes care of b), leaving only c) to deal with. In a modern MS environment though, you can usually expect that there is a corporate CA available, so that means arranging for your appliance to request a certificate from such a CA rather than generating internally. This should be part of setup - so after getting a dns name and ip, display a CSR and request it be signed, offering - as the alternative - to import a pfx file and/or self-generate a cert.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial