SSL woes

Keep getting securty alerts on secure site

[AWildman]

I have a shopping cart system which directs users to a secure site for the purposes of gathering sensitive info.

We've had the same SSL certificate for years, and now, when directing users to the secure site, I get a security alert. Its says, "The name on the security certificate is invalid or does not match the name of the site." When you view the certificate, you see that it hasn't expired and that the domain name listed in the certificate matches the domain name of the secure site that is being viewed.

A warning triangle was on Basic Constraints. All I know about this is that it has something to do with man-in-the-middle attacks.

So, what may be causing this? I'm at a loss.

[AWildman]

Nobody? Well, let me add a little more background. We are changing our domain name to a new one. We have the new domain name and have set up a secure site for the new domain as well as maintaining the original secure site.

When I access the site with Netscape 7.2, I get a message that the site being accessed is the new domain's secure site but that the certificate belongs to the older site. However, the newer site is not being accessed at all. The domain is the older site and nothing on the older site's pages refers to anything in the newer site since for now, the new site redirects to the older site.

Could there be any conflict with this?

[Corey Bryant]

If you changed domain names, that is the problem. When an SSL cert is issued, you enter the domain name, like www.example.com & their [example.com...] is protectedt, but not [example.com...]

Since now you have www.newexample.com, you need to purchase a new SSL cert

-Corey

[AWildman]

We have a cert for both secure sites. Actually, I found the problem, but I'm still confused by it.

I tailed the access logs of both the secure sites since Netscape was throwing up the message about accessing the newer secure site. I'd access the older secure site, get the message, and see no calls to the newer secure site or any activity in its log, nor any references to the newer site in the older site's log. I did notice however, that it hung on a particular background picture.

Now mind you, I'd combed over EVERY piece of css and js that affected the older site and removed all references to the newer site....except for one! ARGH! It killed me! I really don't understand WHY the newer site's log did not have any calls to the picture that was being referenced in the css file. In the older site's log file, it looked as though the picture was coming from the older site.

Oh well. Its solved, but I'm confused.

Thanks for the feedback!

[Corey Bryant]

:) Glad that you got it fixed though!

-Corey