How To Configure Sharepoint 2013 To Allow 3Rd Party Https Redirects

Configuring SharePoint 2013 to allow third-party HTTPS redirects is essential for enhancing flexibility and security. By following these steps, you can unlock the full potential of your SharePoint environment.

To configure SharePoint 2013 for third-party HTTPS redirects, you need to obtain a certificate. This can be done by generating a certificate-signing request (CSR) and supplying it to an SSL vendor or creating a self-generated certificate. Once you have the certificate, you need to import it into the SharePoint webserver.

After importing the certificate, you need to configure IIS bindings to use HTTPS. This involves going to your SharePoint site in IIS manager, right-clicking on the site, selecting Edit Bindings, and adding a binding for HTTPS.

Next, you need to configure SharePoint to use SSL using Alternate Access Mappings. In Central Admin, go to Application Management, then select Alternate Access Mappings. Select the web app you want to change to SSL, edit the default public URL to use HTTPS, and add an internal URL for non-HTTP requests with the zone set to default.

To redirect HTTP to HTTPS, you can use the IIS URL Rewrite module. This module allows you to create a redirect rule that changes the SharePoint site from HTTP to HTTPS. You need to download and install the URL Rewrite module, then open IIS, select your web site, open the URL Rewrite module, add a blank inbound rule, and configure the rule to redirect HTTP to HTTPS.

In summary, to configure SharePoint 2013 for third-party HTTPS redirects, you need to obtain a certificate, import it into the SharePoint webserver, configure IIS bindings for HTTPS, configure SharePoint for SSL using Alternate Access Mappings, and use the IIS URL Rewrite module to redirect HTTP to HTTPS.

Obtaining and Importing a Certificate

Before configuring SharePoint for third-party HTTPS redirects, it is essential to obtain a certificate and import it into the SharePoint webserver. This ensures secure communication between your SharePoint site and third-party HTTPS redirects.

Obtaining a certificate can be done by generating a certificate-signing request (CSR) and supplying it to an SSL vendor or creating a self-generated certificate. The CSR contains information about your organization and is used to generate a unique certificate.

Once you have obtained the certificate, the next step is to import it into the SharePoint webserver. This can be done by accessing the server’s Certificate Manager and following the import wizard. Ensure that you select the appropriate certificate store and provide the necessary credentials for importing the certificate.

By importing the certificate into the SharePoint webserver, you establish a secure connection that allows for encrypted communication between your SharePoint site and third-party HTTPS redirects. This is an important step in configuring SharePoint 2013 for enhanced security and ensuring a seamless user experience.

Steps to Obtain and Import a Certificate
1. Generate a certificate-signing request (CSR) or create a self-generated certificate.
2. Obtain the certificate from an SSL vendor or generate the certificate yourself.
3. Access the SharePoint webserver’s Certificate Manager.
4. Follow the import wizard to import the certificate into the appropriate certificate store.

Summary:

Before configuring SharePoint for third-party HTTPS redirects, obtaining and importing a certificate is crucial to establish a secure connection between your SharePoint site and third-party HTTPS redirects. To obtain a certificate, you can generate a CSR or create a self-generated certificate. Importing the certificate into the SharePoint webserver is done through the Certificate Manager, ensuring encrypted communication and enhanced security for your SharePoint site.

Configuring IIS Bindings and Alternate Access Mappings

Once you have imported the certificate, it is time to configure IIS bindings and Alternate Access Mappings to enable secure communication and redirect HTTP to HTTPS in SharePoint 2013.

To configure IIS bindings for HTTPS, follow these steps:

  1. Open IIS manager and locate your SharePoint site.
  2. Right-click on the site and select Edit Bindings.
  3. Add a binding for HTTPS by clicking on the Add button.
  4. Specify the IP address, port, and SSL certificate for the HTTPS binding, and click OK.

Next, let’s configure SharePoint for SSL using Alternate Access Mappings:

  1. Open Central Administration and go to Application Management.
  2. Select Alternate Access Mappings.
  3. Choose the web app you want to configure for SSL.
  4. Edit the default public URL to use HTTPS.
  5. Add an internal URL for non-HTTP requests with the zone set to default.

Now, to redirect HTTP to HTTPS, we can use the IIS URL Rewrite module:

  1. Download and install the IIS URL Rewrite module from the Microsoft website.
  2. Open IIS manager and select your SharePoint site.
  3. Open the URL Rewrite module.
  4. Add a blank inbound rule, and configure the rule to redirect HTTP to HTTPS.

In summary, to configure SharePoint 2013 for third-party HTTPS redirects, you need to obtain a certificate, import it into the SharePoint webserver, configure IIS bindings for HTTPS, configure SharePoint for SSL using Alternate Access Mappings, and use the IIS URL Rewrite module to redirect HTTP to HTTPS.

Meet the Author

Abdul Rahim has been working in Information Technology for over two decades. Learn how Abdul got his start as a Tech Blogger , and why he decided to start this Software blog. If you want to send Abdul a quick message, then visit his contact page here.