Have You Seen Workflow Lately? Click here to check out all the new features in the latest version.

Supercharge your GE solution! Download a free trial of Proficy Operations Hub, CSense analytics, and more. Learn more about the Proficy 2024 releases, by signing up for one of our upcoming events.

Home
Configure Your Environment
Certificate Handling
Generate Certificates for Workflow 2.6
Workflow 2.5 and earlier does not support the creation of self-signed certificates with the Subject Alternative Name (SAN) property.

Workflow Products Documentation

Configure Your Environment
- User Password Configuration
- Computer Management
- User Interface Controls in the Task List
- Custom Solutions and Displays
- SSL Encryption for SQL Server
- Certificate Handling
  - OPC UA Certificate Handling
    An initial attempt to connect securely to an OPC UA server from the Workflow server will fail due to a missing certificate with the error: The OPC UA server does not have any secure endpoints or the Workflow certificate is not trusted.
  - Generate Certificates for Workflow 2.6
    Workflow 2.5 and earlier does not support the creation of self-signed certificates with the Subject Alternative Name (SAN) property.
  - Modify Server Certificate Folder Location
    You can modify the location of the Workflow server certificates folder.
  - Resolve Port conflicts between prior Proficy Workflow installations and Web HMI
    For existing Workflow installations prior to 2.6, Workflow and Web HMI ports are both set to 8444, making applications installed on the same machine incompatible.

Generate Certificates for Workflow 2.6

Workflow 2.5 and earlier does not support the creation of self-signed certificates with the Subject Alternative Name (SAN) property.

Certificates missing the SAN property are considered to be insecure. If the SAN is missing, Chrome v58.x and later responds with an error when you attempt to connect. For more information, seehttps://developers.google.com/web/updates/2017/03/chrome-58-deprecations and access the Remove support for commonName matching in certificates section.

If Workflow 2.6 is installed on Windows 10 or Windows Server 2016, it generates self-signed certificates using Powershell 5 New-SelfSignedCertificate cmdlet so a SAN can be specified. Workflow 2.6 installations on older operating systems will continue to generate certificates using the previous method. These certificates do not have the SAN property.