Take the 2-minute tour ×
Webmasters Stack Exchange is a question and answer site for pro webmasters. It's 100% free, no registration required.

I would like to ask you a few questions about signed request. As you notice, we must take SSL certificate on 1st Oct. When I researched, we cannot get it as free. I am wondering how you decied that the number of business facebook users must take SSL certificate by payment. Isn't there any other option for taking SSL free such as you provided? Or aren't you going to give the option on Facebook for processing?

I can see there aren't many people realise this matter how big issue is. I tried to call you and ask some question on developer's blog, yet I haven't got any answer.

I hope that I will get the answer for it this time.

share|improve this question

migrated from stackoverflow.com Sep 16 '11 at 8:02

This question came from our site for professional and enthusiast programmers.

Hello and welcome to StackOverflow. Note that this is a site for specific, programming-related issues; this site is not Facebook, and doesn't have any control over Facebook or its policies. –  Piskvor Sep 15 '11 at 9:34
So I guess to make it a valid question on stackoverflow someone has to provide the answer showing him how to use libraries to implement self-signed certificates :P –  sillyMunky Sep 15 '11 at 13:00

1 Answer 1

If you want a certificate which is going to be trusted by most user's browsers (eg. chrome/firefox) then yes, you will have to pay for that.

As for SSL with payments, yes, this is crucial. If you cannot set up SSL you should not take payments, rather try to use a 3rd party to do payment processing.

You are welcome to generate your own certificates. You can generate 'self-signed' (snake-oil) certificates which is fine for use within a company network but users will have to take on trust that it really is the correct site they are connecting to. They should not be making payments to anywhere that uses a self-signed cert (but at least your traffic is encrypted, which is much better than no SSL at all). The browser will usually issue a loud warning if it can't trust the certificate's provider.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.