You need to sign in to do that
Don't have an account?
Sites Secure URL
Sites Explanation:
We have a sites project which is public. The public access settings allow our end-users to login via a guest license and enter their information (no authentication).
Sites URL Setup:
Default URL: http://something.force.com/xyzenrollment
Secure URL: https://something.secure.force.com/xyzenrollment
Custom Web Address: http://enroll.something.com
The Issue:
The Site is not secure. All information entered via the Site by our end-users needs to be secure (i.e. currently http, needs to be https).
Question:
How do I point the users to the Secure URL vs. the Default URL while still keeping the Custom Web Address masking? I changed the Administration Setup > Security Controls > Session Settings > Require secure connections (HTTPS) to checked, but this does not seem to do the trick.
All Answers
Thanks for your reply Paul!
Are there any alternative solutions such as redirects, masking, or maybe something outside of SFDC through the registrar directly (i.e. CNAME)? Is the only solution to dump the Custom Web Address and just use the Secure Web Address (and loose our custom domain name)?
With all the major companies using SFDC, I can't imagine we are the only ones who want a secure connection with our own custom address.
Thanks again Paul. Sorry to hear you were forced off platform by lack of SFDC capabilities.
Our Sites experience has been riddled with caveats and I will definitely be more cautious with the next Sites project... if there is one (will develop off platform). If SFDC is focussed on being an industry leader long term, they need to realize they now have enterprise organizations who demand more functionality and features than a mom & pop shop.
Couldn't agree more. The WYSIWYG interface and shoe-string functionality has a few years to catch up with what I would expect SFDC to deliver. Hopefully others will read this thread and realize some pros/cons when getting involved with Sites. My two cents... don't assume anything and be very careful if you are looking to do anything "outside of the box".
Hi Paul, I think this isn't ready yet. What you guys think about putting the custom domain in an external hosting service, add the SSL and then create a single page with an iframe that will contain the address of the secure address (i.e mysite.secure.force.com). Any implications on this?
We have a customer that has made a huge investment on a development we made and now that we are ready this problema came up, customer needs their https://mydomain.com however seems that this is not possible.
Any ideas will be greatly appreciated.