Setting up my test farm I have a scratch server that i've set up everything on except office web apps, i have that running on another server. I was finally able yesterday to configure a connection between the two servers with SSL, for testing i'm creating my own self-signed certs.
So i have a primary web application i set up yesterday that hosts my community portal, i was able to ensure that it was using SSL over 443 and communicating with the Office web app server to open documents. No problem.
Today i decided to provision in my User Profile service and the mysites, so i created another web application using SSL on 443 and setup a mysite collection in it for UPS to use. Provisioned the service and ran a full sync with AD, was abe to get into my profile site with little issue all looked well.
I moved on to Search and did the same for a search center web application over SSL on 443, had a bunch of issues with search being able to index the https sites. Ran an IIS reset and noticed that 2 of the web applications are not starting...one did but now i have problems with being able to assign certificates that i had created for SSL use to the web app they belong to in IIS, it keeps assigning it but overwriting all of the web apps that use SSL. Stating that i cannot bind more than one web app to 443....
This is my first go round with using SSL and SharePoint...in the past it was all HTTP 80 stuff and i was able to create several web apps on one IP address point them to 80 and all was well.
Is this not the case with SSL and SharePoint? Is there away to have multiple web apps running on a single server/IP using SSL? I hear wildcard certs...but i also hear harbar say they are evil....why?