Hi All,

I already have a SSL on my billing site, I wanted to put my support desk on the same SSL ...

This will not work as the diffrent doman will fire off certificate validation errors.

I therefore have two choices:

1) Buy two SSL certificates, 1 for billing one for support
2) Buy a wildcard certificate.

The wildcard certificates are very expensive and a single wildcard certificate can cost more then two single domain ones.

I have two questions:

1) Do you think I really need a SSL certificate for my support desk or is it ok to have one without it?
The support desk (Kayako eSupport) uses SSL but it does not look professional when it pops up with certificate warnings

Or should I just run the billing off my SSL certificate and not worry about securing the support desk at all?

2) Where can I get rather cheap wildcard SSLs?

Thanks

well, for the support desk I dont think that you need SSL ,


for the wildcard SSLs check
http://www.bright-byte.com/ssl/

I'm thinking maybe I can do just a

https://secure.mydomain.com/supportdesk
https://secure.mydomain.com/billing

and that way I get everything for the price of one certificate

WebWobbler - I like your idea about using just one for that. Personally, I think sub-domains were "cool" for a few years but then they seemed to have gotten overused & now it seems everyone has just gone back to using folders

as far as I see it the only reason for using support.domain.com and billing.domain.com is if they are on two diffrent IPs ... otherwise you can use one IP and one SSL to cover it all ...

Just imagine if the SSL issuers started charging us not only per subdomain but also per subdirectory :D

Originally posted by WebWobbler
I'm thinking maybe I can do just a

https://secure.mydomain.com/supportdesk
https://secure.mydomain.com/billing

and that way I get everything for the price of one certificate

This is similar to the way im going to do it also.. with one ssl cert. seems to be fine and i dont have to worry about multiple ssl's or wildcards or loads of subdomains... so i agree totally with it like this :)

- Buddy

I just can't see the reason for paying for a wildcard SSL ... and you can even offer your customers a shared SSL without wildcards ..