SharePoint 2013-2016 SSL/TLS

MYH 1 Reputation point

Hello everyone, I want to configure SSL/TLS on my SharePoint 16 farm, and I need to take into consideration that the WFM and SSRS were registered using HTTP protocol and I have to use HTTPS instead. Could someone share with me the needed steps to do a scucessful configuration? any documentation or article could be helpful also. Thanks!

SharePoint Server Management
SharePoint Server Management
SharePoint Server: A family of Microsoft on-premises document management and storage systems.Management: The act or process of organizing, handling, directing or controlling something.
2,835 questions
{count} votes

4 answers

Sort by: Most helpful
  1. Trevor Seward 11,691 Reputation points

    For SSRS, if you're using SSRS integrated mode, no changes are needed for the service itself. However you may need to repoint your RDLs to their new URL for the RSDS, if you're using them.


    1. Acquire your SSL certificate covering the FQDN of your Web Application(s).
    2. Import the PFX into the Local Computer\Personal store on all SharePoint servers.
    3. Create a Web Application, if not already created, using port 443 and selecting SSL. Enter an FQDN (URL) covered by your SSL cert.
    4. Once created, using IIS Manager, bind the cert to the IIS site created for the Web Application.

    If the Web Application already exists, you will instead need to update the Alternate Access Mappings with an HTTPS URL and bind your SSL cert to the IIS site. You can drop your HTTP URL. Removing the HTTP URL may break hardcoded paths (i.e. if someone hardcoded an image URL on a SharePoint page.

    For WFM, during the setup, it will ask for certificates. You'll be populating those items as you move through the setup process. More info is at Install and configure workflow for SharePoint Server.

  2. MYH 1 Reputation point

    If the setup of the WFM manager was already done on HTTP protocol, should I remove the WFM from my farm and re-configure and register using the Register-SPWorkflowService -SPSite "https://myserver/mysitecollection" -WorkflowHostUri ""? and the existing running SPD2013 workflows will they be impacted?

    0 comments No comments

  3. Echo Du_MSFT 17,116 Reputation points

    Hello @MYH ,

    1. Un-Register Workflow proxy
      • Go to SharePoint Central Admin >> Application Management >> Manage Service Application >> click on the Workflow Service Application Proxy
      • Select it and from Ribbon click Delete
    2. Register the Workflow Proxy
      Now run the Register-SPWorkflowService in the PowerShell window, I would recommend to use –Force parameter. Register-SPWorkflowService -SPSite "https://myserver/mysitecollection" -WorkflowHostUri "" –Force

    Echo Du


    If an Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  4. Michel Hayek 1 Reputation point

    Hello @Echo Du_MSFT , I tried your solution to register the workflow proxy but I'm getting an error when an SP workflow 2013 is triggered
    error: retrying last request. Next attempt scheduled after x/x/xxx . details of last request: HTTP unauthorized to HTTP://hostname/site/sitecollection/_api/web/lists....
    any idea why i am still getting HTTP and not HTTPS?