We have a client that we develpped a web application for that we also host for them. the users of the application are the client's customers.
since, the client insists that the users see his url on their browsers (https://app.client.com). we had him auto forward the users to us via a link https://app.mycompany.com) while their browser still say "https://app.client.com". but this strategy caused the user's browser to display an SSL error since ssl is registered with our domain name.
Hi, for displaying a correct ssl certificat you need to install that certificate on your client domain,you can't use the certificate which is install on your domain for your client domain.
hope this help
I've been through this, and this is what I learned (interested if there are other options, solutions):
1. https://app.client.com is hosted on a seperate area on you server that you host for the client (or you run a seperate web server dedicated to the client). You server must serve up a seperate certificate (see below) named for https://app.client.com. I know that at least IIP can serve up a different SSL certificate, based on the deployment location. Else you could host a second server dedicated to the client...
2. Your client needs to create a DNS record (CNAME or A-Record) pointing https://app.client.com to your system.
3. You need to purchase (I guess the client pays :-) a new certificate, and configure it to your server, using the client's https://app.client.com domain name.
Good luck (and interested to hear alternatives to the above)...
> 3. You need to purchase (I guess the client pays :-) a new certificate, and configure it to your server, using the client's https://app.client.com domain name.
Actually, the client has to purchse the certificate (since it's their domain). You need to give the proper configuration to the client (includes a server generated certificate, that the cert-authority signs), from which they purchase the certificate, and give that back to you to deploy...