Hi,

I am implementating SSL for the first time.
My client has space on shared server, which has Shared SSL certificate installed on server.

I have deployed site and also using shared certificate using given SSL path to access my payment pages.

But i have one problem that, when ever it enter to SSL it shows one popup msg that

"security certificate doesnot match to the name of the site"

how can i avoide this or what chages i need do?

waiting for +ve reply
Thanks & Regards
Adhik

You can't , You have to buy a totally new cert for that domain. To get rid of the warning.

Thats the problem with Shared Certs.Unfortunaly, you have to buy a dedicated cert. I have had this issue before and it is annoying. :)

Originally posted by adhik
But i have one problem that, when ever it enter to SSL it shows one popup msg that

"security certificate doesnot match to the name of the site"
For the most part, that is the drawback of shared SSL certs. Some hosting providers will setup a virtual directory under the domain of the SSL cert that points back to your site. This will eliminate the "...certificate doesn't match..." message but it may cause a "...going to a different domain..." message with some users -- my guess would be that 80% of the users see the current "doesn't match" message while maybe 20% will see the "different domain" message -- less but still a problem.

Well, a shared SSL is more of a http://thewebhostsdomain.com/site#_or_domainname_or_username/

I think you messed up in generating the CSR

Hi Makie

Is there any other way. Insted of having certificated can we run reguler site under any IP address or virtual folder path
http://shared Server/mysite (normal way to access site) and call only SSL pages in SSL path
https://shared server/mysite (this SSL url for same folder where all file are kept).

coz problem is that when i access with whole site with my domain name (http://mydomain.com/)
and for ssl pages with (https://mydomain.com/myadmin/) it shows me popup alert of securiy.
but if i transfer contal to https://shared server/mysite, for ssl pages through it wont show any such popup as certificate is for same domain (for shrared server) but here i loose my cookie and seesion containts which are very important as i m switing between domain names.

so is there any way to do like this.
that i can map my hole site any virtual folder of shared server so that i can access that using shared server name and ssl through shared server ssl path (no domain switch), just redirecting user from mydomin.com to above url, i can achive both tasks.

Thanks & Regards
Adhik

Originally posted by adhik
Is there any other way. Insted of having certificated can we run reguler site under any IP address or virtual folder path
http://shared Server/mysite (normal way to access site) and call only SSL pages in SSL path
https://shared server/mysite (this SSL url for same folder where all file are kept).

coz problem is that when i access with whole site with my domain name (http://mydomain.com/)
and for ssl pages with (https://mydomain.com/myadmin/) it shows me popup alert of securiy.
but if i transfer contal to https://shared server/mysite, for ssl pages through it wont show any such popup as certificate is for same domain (for shrared server) but here i loose my cookie and seesion containts which are very important as i m switing between domain names.

so is there any way to do like this.
that i can map my hole site any virtual folder of shared server so that i can access that using shared server name and ssl through shared server ssl path (no domain switch), just redirecting user from mydomin.com to above url, i can achive both tasks. You can but image wise, www.mydomain.com is more impressive that www.somesharedhost.com/mydomain.

To preserve your cookies when bouncing off to another domain, I simply pass the cookie values as URL parameters with all references that point to the other domain.

The main point of using Shared SSL facility is that you do not need to purchase your own certificate and do not need to go through all the process of certificate purchase. I think this point makes the Shared SSL facility more popular. :D

Hi shift4sms

Yes, thanks a lot, my values of page are not fixed that values are stored in cookie. basically its shopping site. i cannot predict number values that i need to carry.

Also my whole appliation is ready now, and for implentation of ur solution i will need to change the whole logic.

Originally posted by Shikha
The main point of using Shared SSL facility is that you do not need to purchase your own certificate and do not need to go through all the process of certificate purchase. I think this point makes the Shared SSL facility more popular. :D I'm not sure where you came to that conclusion? "security certificate doesnot match to the name of the site" is a shared certificate drawback as well as "...going to a different domain..." and also the not so impressive "www.somesharedhost.com/mydomain".

To me, a shared SSL cert is never a good choice if the cert will be used by site customers -- internal usage is fine. Company image wise, the $100 or so a year is well worth the investment...

:cartman:

Regarding...

To preserve your cookies when bouncing off to another domain, I simply pass the cookie values as URL parameters with all references that point to the other domain.
<--->
Yes, thanks a lot, my values of page are not fixed that values are stored in cookie. basically its shopping site. i cannot predict number values that i need to carry.
------------------------------------------------------------

What if the URL that referenced the cookie used dynamic parameters so it could always match when it used the second domain?