PDA

View Full Version : SSL confusion!


WongP
06-May-2003, 08:03 PM
I have decided it is time to upload a test version of my site and I need some explaination of the ssl side of things.

Here's the story: I am using the Wizard function to configure Network settings for the first time. It does a remarkable job of finding my folders on the server and the correct path to my cgi-bin. The first error I have encountered is in relation to the Secure Server CGI-BIN URL prompt.

The Wizard needs to know the URL of the cgi-bin directory on the secure server and I type an address. The following message is bounced back, "Your web server is not configured for secure communications (no ssl lisence). Contact your ISP". My ISP were quick to respond saying that "You have not purchased an SSL certificate (service) from Areti and as such you do not have SSL capability in your hosting package." Fair enough, but it prompts a couple of questions.

1. I have selected e-clear as my PSP, so they will deal with the ssl side of things, won't they? So I don't need to purchase a ssl certificate do I?

2. I have enabled ssl on checkout and log in only - under Business Settings - so then again, I don't need a ssl certificate as the psp will handle it (except for the log-in).

I would grateful if somebody could explain the full picture to me. Do I need to get one or not? Many thanks!

pinbrook
06-May-2003, 09:38 PM
Normally if you are using a PSP you don't need SSL

Check the documentation with e-clear that they use SSL, if they do, you don't need to

WongP
07-May-2003, 09:03 AM
Thanks for your reply. Ok, so if I don't need to get ssl, then when I am prompted for the URL of the cgi-bin on the secure server at the Network Settings procedure, what should I put in?

pinbrook
07-May-2003, 10:45 AM
Have you got the check box ticked.....business settings, payments and security SSL on

turn it off (and any other SSL options if there are any) then you won't get asked for the SSL url

WongP
08-May-2003, 12:47 PM
Thanks. That seems to have done something. There are a number of other issues that have cropped up, now that I can see the site on-line!

I'll be back ...