Reputation: 5399
I've written an application that uses some flash components. To allow these flash components to work with other machines, I need to accept certificates from these machines or skip certificate errors permanently on user machines to accomplish this.
I tried the following, but none of this worked for me:
Nothing stated above was able to help me.
I also have read/heard 'warn about invalid site certificates' setting in Internet Explorer (this article states it exists), but I haven't find it in the Internet Explorer 9 settings.
Could somebody suggest any way of how certificate warning can be skipped?
Thanks in advance!
p.s. Here is what the warning states:
Upvotes: 2
Views: 8052
Reputation: 3091
Yes, I'm fully aware that this is a very old thread.
But after doing research on this problem, in Windows 7, I came up with a new solution, one which actually works -- and one which I haven't seen suggested anywhere online.
I'm posting it here (which might or might not be the ideal place for it!!) on the assumption that the nature of my solution potentially makes this a valid fix for ANY version of Internet Explorer! As a fix, it's a bit conventional, so I'm surprised I've never seen anyone propose it before.
.
This is a fix for when the IE browser reports a red 'Certificate Error' notice in the URL address bar.
.
How to create 'Console1.msc' -
Upvotes: 0
Reputation: 57125
Adding the certificate to the Trusted Root CA store will resolve the "The security certificate presented by this website was not issued by a trusted certificate authority." message. Note that you need to trust the root certificate that the server's certificate chains to, which may or may not be the same certificate that the server sent.
The "Warn about certificate address mismatch" checkbox resolves the "Security certificate presented for this website was issued for a different website's address" error only. It's unsafe to uncheck this box because it applies to all sites.
Changing "Check for publisher/server certificate revocation" will not help you.
If you're doing this only for test purposes, consider simply running Fiddler in HTTPS-decryption mode. Fiddler will hit the certificate error and you can ignore it for the lifetime of the Fiddler session.
Alternatively, your best approach is to simply fix the certificate on the other server. If it's self-signed and you don't want to pay for a CA certificate, at a very minimum you should update the self-signed certificate to contain the proper CN or SubjectAltName to match that server's hostname.
Upvotes: 3