Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

WSS v3 - Moving to HTTPS Connection

  Asked By: Johanna    Date: May 22    Category: Sharepoint    Views: 1781

We recently implemented an intranet using WSS v3 that is accesible
only through a VPN connection. We would now like to change access to
the site to be HTTPS, but need to figure out what happens to links
that are based on the internal URL (192.168....). For example, if we
change the site to HTTPS access and then someone clicks on a link list
item that was based on the VPN path, do they get a page not displayed
error(seems like that would be the result)? If so, can this be fixed
with managed paths (ie. map 192.168 to HTTPS address)?

Does anyone know of any other issues to look out for when making this



6 Answers Found

Answer #1    Answered By: Jacklyn Burnett     Answered On: May 22

You need to put the https:// address in the Internet Zone for that Web
Application. WSS will generate the correct URLs for SharePoint content based  on
that. In Central Admin, Central Administration > Operations > Alternate Access

Answer #2    Answered By: Breann Beach     Answered On: May 22

You can either add a Zone or change  the Default Internal URL
from Central Admin > Operations > Alternate Access Mapping. If you only
need a single URL, I suggest changing the AAM. This is the simplest way to
change over to SSL.

Answer #3    Answered By: Timothy Hall     Answered On: May 22

Your suggestion has the added benefit of forcing everyone to use SSL, whether
they type the address in as http or https.

Answer #4    Answered By: Joanne Greer     Answered On: May 22

Thank you both for the quick response. Just a quick point of
clarification - If I understand you correctly, then if I add the new
HTTPS address into AAM, then any links (including those manually
created for link lists) that refer to the internal  IP, will still
work, because AAM will indicate that for example
https://companyweb.com = http://192.168.xx.xx.

I apologize in advance if I'm not using the right terms, as I'm new
to the AAM functionality.

Answer #5    Answered By: Cathy Cameron     Answered On: May 22

If you want to continue to access  the Web application from two distinct
URLs, you will need to ADD an alternate access mapping instead of
changing the default. Do this:

1. Browse to Central Administration > Operations > Alternate Access

2. Add Internal URLs

3. Select the http://192.168.x.x Web App (mapping collection)

4. Enter https://companyweb.com and select zone. If you are not
extending and mapping, this is probably Default.

5. Assign IP address in IIS Manager, Install Certificate, change
DNS if necessary

Answer #6    Answered By: Kerri Steele     Answered On: May 22

All have to remember to use tinyurl for this email forum.


Didn't find what you were looking for? Find more on WSS v3 - Moving to HTTPS Connection Or get search suggestion and latest updates.