Topic: SSL

I have a widget configuration movie that authenticates a user against a remote web service on our end prior to letting them complete the configuration.  I notice when I call the web service on an https (SSL) URL, the process fails and it is as if the Flash content doesn't receive any XML, whereas with a regular http call, it works fine.

Is this expected behavior?

2

Re: SSL

I am not the Flash expert in the house, but I am willing to bet it has to do with your crossdomain.xml file on your servers. You might need to enable chumby.com cross domain access. Give that a try, I will pass this along to one of our Flash gurus.

Re: SSL

emansouri, as jt mentioned, you'll need a policy file. sounds as though you may have one in place already. if so, you may need to set the 'secure' attribute to false (to enable an http swf to access https content).

see the bottom of this page for more info: http://livedocs.adobe.com/flash/8/main/ … 01621.html

if that does not does not help let us know

Re: SSL

Hi emansouri,

Another thing to consider is to make sure the server you're connecting to has a valid certificate. If you go to the site through a browser and it shows a dialog saying the certificate is invalid, you can click through and get to the site. But in Flash, if the certificate is invalid, it will silently fail.

If the certificate is good on the server side, then also make sure that the system date on the chumby is accurate. Flash will see the certificate on the server and compare it to the system date, and if it's off by more than a few months, it also fails silently.

The joys of working with Flash! wink

Good Luck,

iBrent

Re: SSL

Thank you all for your responses.

It turns out adding the secure="false" attribute to the allow-access-from element in my crossdomain.xml policy file did the trick.

Thanks again!

Re: SSL

for the most 'insecure' approach to getting around the flash player security sandbox issues, use this in your crossdomain.xml

<?xml version="1.0"?>
<cross-domain-policy>
  <allow-access-from domain="*" secure="false" />
</cross-domain-policy>