SALES: 1-800-867-1380
The topic you requested is included in another documentation set. For convenience, it's displayed below. Choose Switch to see the topic in its original location.

Managing Certificates (Workflow Manager 1.0)

Updated: October 24, 2012

Several cmdlets are available for managing the certificates that secure communications for Workflow Manager.

Anytime you plan to set or change any of the certificates for a farm, you must first stop all of the nodes in the farm using the Stop-WFHost cmdlet, then restart each node using the Start-WFHost cmdlet to load the new configuration.

Specifying Workflow SSL Certificates

The Workflow Manager SSL certificate secures internal communications between nodes in the farm. You can use the Set-WFCertificate to change the certificate after the computer joins a farm.

Specifying the CertificateAutogenerationKey

The Set-WFCertificateAutoGenerationKey cmdlet changes the key used to secure auto generated certificates.

Set-WFCertificateAutoGenerationKey cmdlet re-generates the certification authority and the certificates.

Propagating Workflow Manager Certificate Changes

The Update-WFHost Update-WFHost cmdlet propagates any changes in farm certificates made with the Set-WFCertificate cmdlet to each machine in a farm. Use the following procedure:

  1. Call Set-WFCertificate cmdlet with the new certificates.

  2. For every machine:

    1. Stop the workflow services on the computer by using Stop-WFHost.

    2. Update the certificates on each machine in the farm by running Update-WFHost.

    3. Restart the workflow services on each computer in the farm by running Start-WFHost.

Displaying Certificate Data

The Get-WFFarm cmdlet displays the configuration information from the certificates described in this section.

Workflow Manager 1.0 MSDN Community Forum

Build Date:

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

© 2014 Microsoft