SSL certicates and new facebook requirements

We don't issue SSL certificates at all. Those need to be purchased from a 3rd party and installed on your server. For more information on where we purchased our SSL certificate, and where you can get your own, along with some instructions on installing it, you can check out our SSL guide below:
www.sourcecoast.com/jfbconnect/docs/comm...ficates-for-facebook

If your hosting provider has a wildcard SSL certificate for many sites, that usually works too, but we haven't tested it.

In no way is the SSL requirement made by JFBConnect. Facebook has the requirement for SSL certificates if you want your site shown in a Facebook Page or Canvas/App view. The new requests system in 4.1 uses the Canvas/App, which is why the SSL certificate is required for that too.

Hope that all makes sense,
Alex

Sounds good. It's a bit annoying that Facebook requires SSL, but there is a good amount of information they pass to the site when visited through Facebook. Nothing too sensitive, but having an SSL certificate on your site just makes that communication more private.

The only thing that requires SSL is the Page Tab and Canvas integration.. and the new Request system relies on the Canvas App being setup properly. All other features you've used until now will still not require an SSL cert.

Anyway, certificates are pretty cheap now, and for the new requests features, we think it's well worth $10, $20, or more depending on your site.

Alex

Philip,
That's correct. An SSL certificate is tied to a domain name. Most shared SSL certificates get around this by re-naming your site, so instead of going to 'domain.com', you have to go to 'domain.sharedssldomain.com'. This routes your site through the domain (sharedssldomain) that the certificate is valid for, but doesn't present your real site's domain to the user.

Facebook requires that your real domain be used, to prevent forgeries and misleading your users. So if your shared SSL certificate requires you to use a different domain name than the Site and Canvas URL set up in your Facebook Application, the browser will throw warnings/errors because of the different domain names. For more information on Hostgator's shared SSL, see:
support.hostgator.com/articles/ssl-certi...ave-browser-warnings

We definitely agree that a dedicated SSL certificate is worth the trouble and cost, and that shared ones can cause issues depending on the configuration.

Hope that helps explain the cause, and thanks for your feedback,
Alex

It shouldn't be anything with our affiliate link. That's a simple link, there's no image or any other 'insecure' content there.

For the content plugin, it could be because of the other social widgets. Can you try turning them off and see if that fixes the issues? The LinkedIn Share button, especially, can try to load it's images over http instead of https, causing those mixed security warnings.

Let us know how that goes!
Alex