This content has been marked as final. Show 6 replies
I am also having the same problem.... Using an SSL endpoint that works in Firefox but NOT in Internet Explorer. If anyone has a solution I would be eternally grateful!
<channel-definition id="my-cfamf-ssl" class="mx.messaging.channels.SecureAMFChannel">
<endpoint uri="https://mydomain.com/flex2gateway/" class="flex.messaging.endpoints.SecureAMFEndpoint"/>
Are the certificates self signed? I have gotten issues like this to work when I have certificates that are signed by a real CA, might be able to do some kind of CA install for the your self signed certs but not sure how to do that.
Basically looked at the certificate for the answer to the problem.
Our certificates on the server are issued by Network Solutions Certificate Authority and expire December 2007. Why would IE have a problem with certificates when Firefox does not?
Here's an update...
It does not appear that IE will allow you to use Flex apps using an SSL encrypted channel. We thought the problem was self-signed certs in our dev and test environments, so we bought legit certs from Thawte and it still does not work. Does this mean we won't be able to use Flex in IE? If this is the case, this is really bad for Adobe since enterprise apps cannot really run on unsecured channels and most people still use IE. We're heavily invested in this and need some answers.
I hope that's not the case, we have a lot of money invested in this as well. Someone please tell us that this will work!
Do this, and it will fix it:
Put this in your channel definition inside the services-config.xml file:
This fixed it for me. Msg back if you have any questions.