I am working on a site for a credit card processing for merchants company which requires a merchant login page. I set the page up through the actual credit card processor they use and all is well except that the actual login page is not secure. Surprisingly to me the processor does not require the login page to be secure, though it leads of course to an ssl page. It seems like overkill to enable ssl for the entire site. Would this be a good place to enable a shared page that came with their hosting package or is there a better way? They are on linux. At this point, I think they only need one secure page.
Thank you!

Hi there,

Sorry no one got back to you sooner with this. Using the shared SSL for that page is a good idea - better safe than sorry when it comes to security. The only potential issue I see is the URL being different. So for example if your login page is usually

http://www.mydomain.com/admin/login.php

the shared secure URL will be

https://www##.safesecureweb.com/domain/admin/login.php

There are two things that might come up. One, since your the domain name changed, you will lose any session variables you have. Two, if the merchant is configured to expect the post to come from a specific domain, it might not like seeing it from www##.safesecureweb.com.

In either case a quick test will help identify any issues. You can find the shared URL in your control panel or you can give a ring to support and they will be able to help.


Regards,
Dave

Thanks Dave,
I am attempting to do this and will check back if necessary! I have received the necessary info from support and hope I can get it working.
Best,
Wendi