Publishing players on HTTPS pages

by Administrator on 01-19-2009 03:03 PM

Formerly, if you published a player on a page served by HTTPS, some browsers would generate a security warning. We've modified the JavaScript publishing code and added a secureConnections configuration parameter, so that you can now publish a player on an HTTPS page and not generate this security warning. Read more about how to publish a player on an HTTPS page.

Note that this does not cause the Brightcove player to use HTTPS; instead, it simply prevents the viewer's browser from generating security warnings that might otherwise be triggered by the player's communications.

Comments
by joe_sf on 04-29-2009 09:00 PM

Grant,

 

I was playing around with this a bit, because we have an iframe that is served over https, and within that iframe we display the brightcove player.

 

I added the <param name="secureConnections" value="true" /> to the object tag. In addition the JS files are loaded also over https.

 

This works well on most browsers, but on Opera and Netscape Navigator I am still getting the security warnings about the secure and insecure content.

 

BTW, this happens both if the iframe is loaded from a http and https page.

 

Version Info:

Opera 9.64 build 10487 - Flash 10.0.2.54 on Win XP Pro

Netscape Navigator 9.0.0.6 - Flash 10.0.2.54 on Win XP Pro

by Administrator on 05-01-2009 05:06 PM

Unfortunately we don't do any official testing on Opera or Netscape Navigator so we won't be able to determine their specific behavior. They may manage their security dialogs in a manner that is not compatible with this feature. We primarily focused this HTTPS setting to remove security dialogs within IE.

 

For a comprehensive list of our officially supported platforms please note:

http://help.brightcove.com/publisher/docs/intro/sys-reqs.cfm

 

 

Thank you!

Bob Mason

CTO

by pumukli5 on 08-06-2009 07:24 PM

I checked out this page, http://support.brightcove.com/en/docs/publishing-brightcove-player, but as i see that code is for BC 3. Can I just assume and use the same parameters for previous codes, like below

 

- <param name="secureConnections" value="true" /> would be like this: config["secureConnections"] = true;

 

- <script src="http://admin.brightcove.com/js/experience_util.js" type="text/javascript"></script> would be like this: <script src="https://sadmin.brightcove.com/js/experience_util.js" type="text/javascript"></script>

 

Should that work???