Ok, I've got a problem with a customer and I need your help. I am building a print management system on one of my domains through you guys (which has anSSL cert).The original plan was that the employees of two of our sister companies were going to use that sytemthrough our domain.Now the sister companies wish to have the print management system I'm building show up on their domains too (without any trace of our company/domain name). As far as multiple domain name pointing to the same content, I know I can point the domain here and have the content show the same folder/contents. As I understand it,I'll have to programatically change Company Names/Logos within pages based on thedomain used to load the content. My question is this... will the SSL cert for https://secure.domain1.com work under the different domain names (https://secure.domain2.comand https://secure.domain3.com)? My guess is no. If not, would I then have to purchase 2 addl SSl Certs? Will the new SSL address https://secure.domain2.combe able to show the content of the original site at https://secure.domain1.com? Does this make any sense? MIke Post Edited (Mike Reilly) : 10/11/2006 6:38:07 PM GMT
Mike 1) You cannot put multiple certificates on a single account. This is an IIS restriction (1 cert per virtual server) 2) Technically, the data transfer is secure whether the name matches or not. You can still access https://domain1.com and https://domain2.com securely. The problem is that most browser will pop up a warning telling user that the name doesn't match Bruce DiscountASP.NET www.DiscountASP.NET
Thanks Bruce. I think I've seen that before on another site. Correct me if I'm wrong, but the alert (saying that the name doesn't match) shows the actual domain that is certified, so our domain/company name would be exposed, right? Since I can't put multiple certs on 1 account, is there any easy way to have the data replicated across three seperate accounts (so I can have three distinct SSL certs, 1 per company)? I would think I could justupload the asp files into 3 seperate FTP accounts. Is there any problem with one domain calling a database on another domain (I haven't tried yet)? If that's possible,I think I'll just keep 1 domain with the database and move the other 2 domains to DASP as individual accountswith "mirrored" codeconnecting to that same database. So I'd have three domains, each with an ssl cert https://www.domain1.com - with a database and code https://www.domain2.com - copy code from domain1 to here and let access the domain1 database https://www.domain3.com - copy code from domain1 to here and let access the domain1 database Does that sound like it would work?
