We have a force.com site which has a simple lead form. We want to use a custom domain name like https://www.companyname.com/leadform as our url which we can use for marketing. I know we can register a custom domain and point the cname record to the force.com site url. But is it possible for me to have a ssl certification on companyname.com point to salesforce site page? Has any body come up with a solution for secure pages using custom domain like https://www.companyname.com/leadform as an example? Buyan
The answer to this question has changed with the SU14 release. See Configure a Custom Domain for Your Community which provides instructions that primarily involve contacting SF Support and the caveats highlighted below.
Bunyan, take a look at the Sites FAQ which says the following:
Q: Does it support HTTPS custom URLs (not force.com URLs) with our own certificate?
A: Not at this time
Q: Can i specify my own SSL certificate if i use a CNAME to brand my URL
A: SSL certificates specify an IP address and at the current time we do not provide a feature to host SSL certificates for sites other than the default domain force.com.
From the above, unless something has changed, I'd conclude that at this time it's not possible to do what you desire.
To the contrary of the linked documentation from @crmprogdev, as of at least August 2013 Salesforce does support this scenario.
SFDC Help: Adding a Domain
A couple of key points:
Answers to the questions below
This is done using your DNS
A URL like this one:
Salesforce provides tools for managing certificates within your org. You would use these tools to generate a Certificate Signing Request (CSR) and have that request signed by the CA and then you can upload the certificate into your org.
Per that help document, you can contact Salesforce and they can associate your force.com site with the SSL certificate which you uploaded. After that is complete, your force.com site will be available using your SSL certificate via your custom web address defined on your site.
Private SSL certs don't work. We've been on the road once - did everything as instructed by document: get CSR from SF, cert signed by a CA, uploaded the cert. In the end, it didn't do a thing for the site intended (with the cert URL configured as primary btw and CNAME rediret set up). After a 3 1/2 months case, SF finally said, "nope, feature wouldn't be production available until at least Winter '14". The exact quote from the case owenr was
Now Spring '14 is almost out, and the feature is still nowhere to be found.
For completeness sake...
create an AWS account and run ngnix in a reverse proxy configuration. Setup your certificate and domain against that IP address and you can then forward website requests to salesforce using SSL and your own domain. It goes against the no hardware stance but since salesforce is a multi-tenant environment and SSL essentially requires a single IP/server per certificate they are going to be hard-pressed to support a large number of SSL custom domains as a general feature.