New Site Collection isn't secure (i.e. SSL) like our other

Question

I created a web app (sharepoint2.xyz.com), then extended it (AAM) to sharepoint.xyz.com. I also created a Site Collection called sharepoint2.xyz.com with our subsites under that (to mimic our 2007 install). All above sites & subsites utilize SSL successfully (https://sharepoint2, etc and https://sharepoint, etc. The problem is I've created a new Site Collection (sharepoint2.xyz.com/sites/NewSite) and it works using either the sharepoint2 or sharepoint URL, however, but not using the https URL. SSL does not work. In IIS, we had previously defined both http and https for sharepoint2.xyz.com but only http for sharepoint.xyz.com. In an attempt in resolving this issue, we added the binding for https to sharepoint.xyz.com in IIS but that causes sharepoint.xyz.com to be completely inaccessible.

Could someone please offer some advice? Thanks!!

Answer 1

The sharepoint.xyz.com, from what I have gathered, is the URL you want to use. This site should have the SSL setup on it, not sharepoint2. If users are going to use sharepoint2.xyz.com securely, that'll need the SSL as well, but I think that's not the case. If it is, then you need a unique IP per site running SSL, so you'll need 2 IPs for both sites.

I think you want the following

Web App default http://sharepoint2.xyz.com AAM internet https://sharepoint.xyz.com AAM extranet http://sharepoint.xyz.com

Again, if you want https://sharepoint2.xyz.com will need it's own IP in IIS.

Check out this blog post, might help clarify it a little http://sp365.co.uk/2011/12/friendly-vanity-urls-and-sharepoint/