Setting up the Windows App Client

Scenario: You want to set up and work with the Windows App client on the Desigo CC Server with local web server (IIS) or on the remote web server (IIS) hosted on the Desigo CC Client/FEP.

For working with the local Windows App client on the local web server (IIS) you can leave the web communication as Local.

For working with the remote Windows App Client, it is recommended to secure the communication between the Desigo CC Server and the remote web server (IIS).

In this workflow for securing the communication between the Desigo CC Server and the remote web server (IIS) Windows store based certificates are used.

If you are upgrading from Desigo CC V4.x (and not using code-signing certificate in V4.x) to V5.0, are not able to work with the Windows App Client after the upgrade. This is because starting Desigo CC V5.0 SMC verifies code signing for website/web application certificates. The certificate must have code-signing feature to prevent your systems from any security threats and remote attacks.

For the purpose of code signing, you can use either SMC-created certificates or procure certificates from a trusted Certificate Authority (CA). The certificate can be a host certificate with a private key or a self-signed certificate. However, it is recommended to secure the communication with the self-signed certificate.

NOTICE

Validity of Self-Signed Certificates

Self-signed certificates allow local deployments without the overhead of obtaining commercial certificates. When using self-signed certificates, the owner of the Desigo CC system is responsible for maintaining their validity status, and for manually adding them to and removing them from the list of trusted certificates.

Self-signed certificates must only be used in accordance with local IT regulations (several CIO organizations do not allow them, and network scans will identify them). Importing the commercial certificates follows the same procedures.

You must ensure the compliant installation of the trusted material on the involved machines, for example, on all Installed Clients. In some organizations, this must be done by the IT organization.

Reference: For background information, see the reference section.

Workflow diagram:

Prerequisites:

• On the Server station:
• (Only applicable for Server with local web server (IIS)): IIS is installed and configured according to the OS installed. (see Install IIS in Complete the Installation Planning Requirements).
  - You have verified the existing Application Request Routing (ARR) installation.
  - (Optional) A dedicated IIS User is created and assigned to the IIS_IUSRS Group.
• A project is created and the history database is linked to it.
• (Only applicable for Server with remote web server (IIS)): To set the Web Server Communication = Secured over CCom port.
  - The Windows store based root and host certificates (used for securing CCom port) are imported in the appropriate certificate store and set as default.
  - The root certificate (.cer file) of the CCom host certificate is available in the Trusted Root Certification Authorities (TRCA) store of the Local machine certificates store.
  - The CCom host certificate's subject name must match the server name configured in the Client/FEP project.
  - If a multi-host certificate is used as a CCom host certificate, then the Subject Alternative Name (SAN) property must contain all its possible host names.
• On the remote web server (IIS) hosted on Client/FEP station:
• The user that you are about to configure as a web application user is
  - a member of the IIS_IURS group and
  - added with Allow log on locally as service rights and
  - added in the list of allowed users in the Project Shares expander of the linked Server project.
  - (Only applicable when the project that you are about to link to the web application is in distribution with other projects) added in the list of allowed users in the Project Shares expander of all the systems (projects) in the distribution with system (project) linked to the web application.
• The root certificate (.cer file) of the CCom host certificate of the linked Server project is imported in the Trusted Root Certification Authorities (TRCA) store of the Local machine certificates store.
• You have stopped the Default IIS Website using SMC.
• (Only applicable only for the third-party websites/web applications) You have reviewed the tips for working with the third-party websites and web applications.
• The website/web application certificate:
  - (recommended) Use the default set self-signed certificate or the self-signed certificate created at the time of website/web application creation.
  - The self-signed certificate is imported in the Personal, as well as the Trusted Root Certification Authorities store of Local machine certificates in the Windows Certificate store.
  - If a host certificate is used as a website/web application certificate, the host (.pfx) along with its exportable Private key and its root (.cer file) are imported in the appropriate Windows Certificate store. Otherwise, a chain validity message displays.
  - A host certificate is issued for the host name provided in the Host name field during website creation. Otherwise, you may encounter a Network Error (dns_unresolved_hostname).
  - If a multi-host certificate is used as a website/web application certificate, then the Subject Alternative Name (SAN) property must contain all its possible host names. (see Add Entries in the V3.txt File for Creating a Multihost Certificate).
• To run the Windows App client on IPv6 network enabled systems, see Configure the Web Server to Run on the Dual-Stack (IPv4 and IPv6) Network.

Steps:

1 – Modify the Server Project Parameters

For Launching Windows App Client on the remote web server (IIS), it is recommended to set the Server Communication as Stand-alone and the Web Server Communication as Secured in the Communication Security expander in SMC. For Server with a local web server (IIS), you can, however, leave the Server Communication as Stand-alone and the Web Server Communication as Local.

You also must share the Server project with the website/web application user using the Project Shares expander.

• The Server project that you want to link to web application is after creation / restore available under the Projects and is Stopped.

1. In the SMC tree, select Projects > [project].

2. Click Edit .

• Some fields of the Server Project Information and Communication Security expanders are enabled.

3. In the Communication Security expander, do not modify the default (Stand-alone) Communication mode.

4. In the Communication Security expander, provide the Web Server Communication details as follows:

• For working with local web server (IIS): Change the default Communication mode (Disabled) by selecting Local from the drop-down list. This enables the communication between the CCom port and web server (IIS), without certificates.

• For working with remote web server (IIS): (recommended) Change the default Communication mode as Secured from the drop-down list. This enables a secured communication between the CCom port and web server (IIS).

• Configure a unique the CCom port number, if required, by changing the default.

• (Applicable only for Web Server Communication as Secured) Verify the default set host certificate for CCom port. For more information, see tips.

5. Using the Project Shares expander, you need to share the Server project with the website/web application (IIS) user as follows:

• Select the Share Project check box to share project folder of the current project.

• If required, type in the Base share name to change the default set, the Project name.

• Click Add to add the website/web application user to the list of Group or user names using the Select User or Group dialog box.

6. Click Save Project .

• If you have changed the Communication Security settings including the Web Communication mode, CCom port, or a CCom Host certificate, a message displays indicating you that you must align the Web applications on Client/FEP linked with this modified Server Project.

 

2 – Create a Website

Using SMC you can create a new website on Server with local web server (IIS) or on remote web server (IIS) hosted on Client/FEP.

1. In the SMC tree, select Websites.

2. Click Create Website .

3. In the Details expander, enter the website details as follows:
   a. Type a unique name for the website.
   b. Click Browse to change the default location [installation drive:]\[installation folder]\[WebSites] and to store the website files at desired location.
   c. Provide the host name: Full computer name, DNS name or IP address of the local host (web server IIS).
   d. In the Certificate issued to field, it is recommended to use the default set self-signed certificate
   Alternatively, you can create a new self-signed certificate by clicking Create, if no default self-signed certificate is already set. or
   Click Browse to select a host or self-signed certificate from the Personal tab of the store location Local machine certificates using the Select Certificate dialog box. (see Tips for Selecting a Certificate for a Web Site)
   e. Browse for and select a website user using the Select User dialog box. This user must be a member of the IIS_IUSRS group. Otherwise, a message displays asking you to add the selected user to the IIS_IUSRS group, or to select another user from the IIS_IURS group.
   The user must also have Allow log on locally as Service right set. For more information, refer Cannot Create or Save Website in Troubleshooting Websites and Web Applications.
   f. Provide the password of the selected website user.
   g. Do not change the default port number for the HTTPs port unless you have already configured a website that uses that same default port number.
   To change the HTTPs port number, type or use the UP and DOWN arrows to specify a port number in the range of 443 through 65535.

4. Click Save .

• A confirmation message displays.

5. Click OK.

• The website is created, activated, started, displayed as a child under Websites in the SMC tree and is selected by default.
  NOTE: If a website creation fails, and on opening the SMC log file, located at
  [Installation drive]:\[Installation folder]\GMSMainProject\log, the SetPermission exception displays. (See Unable to Set Security Permissions on Websites/Projects Folder.)
  For other website and web application troubleshooting topics, see Troubleshooting section.

• The HTTPs website URL, when clicked, opens the Desigo CC web page in the default browser. However, you can launch a Windows App client only using a web application URL.
  You can also copy the website URL using the Copy URL button and paste it in the browser.

• It internally also enables the Proxy for the Application Request Routing (ARR) Cache in IIS which is required for Windows App client connectivity.

NOTICE

Validity of Self-Signed Certificates

Self-signed certificates allow local deployments without the overhead of obtaining commercial certificates. When using self-signed certificates, the owner of the Desigo CC system is responsible for maintaining their validity status, and for manually adding them to and removing them from the list of trusted certificates.

Self-signed certificates must only be used in accordance with local IT regulations (several CIO organizations do not allow them, and network scans will identify them). Importing the commercial certificates follows the same procedures.

You must ensure the compliant installation of the trusted material on the involved machines, for example, on all Installed Clients. In some organizations, this must be done by the IT organization.

 

4 – Browse a Website or Web Application URL

You can launch a Windows App client by browsing the web application link on the local web server (IIS) or on the remote web server (IIS) hosted on a Client/FEP or on remote computer other than web server (IIS). For this you must install the website/web application certificates in the appropriate Windows certificate store.

You can launch the Windows App client by browsing the website or web application URL in the supported browsers such as Microsoft Edge, Chrome, Firefox and Internet Explorer 11 onwards.

NOTE:
It is recommended upgrading and staying up-to-date on the latest browser version.

The following procedure provides the steps for launching the Windows App client for the very first time by installing the website certificates. The steps may vary; for example, the Certificate Error: Navigation Blocked page may not display, if the website/web application certificate is already installed.

1. You have reviewed the tips before launching the website or web application URL.

2. In the SMC tree, select the website or web application.
   NOTE: Clicking the website/web application URL in the SMC results in opening the Desigo CC web page in your default browser. It is recommended to launch the Windows App client using either Microsoft Edge, Chrome, Firefox or Internet Explorer 11 onwards.

3. Click Copy URL to copy the HTTPs URL of a website/web application.

4. Launch the browser.

5. In the address bar, paste the copied URL.

• The Certificate Error: Navigation Blocked page displays. This error occurs if the self-signed or host certificate is not already available in the Windows Certificate stores. Usually this error does not occur for the commercial certificates.

6. Install the website certificate.

7. Close the browser.

8. Re-launch the web application HTTPs URL.

• The error message Certificate Error:Navigation Blocked disappears and the Desigo CC web page with thumbnails for Windows App client displays.

9. Install the web application certificate for verifying the signature when downloading the application in the appropriate Windows certificate store.

10. From the Desigo CC web page, depending on the client type, click the Windows App Client thumbnail and follow the installation wizard prompts that display (in the section on Starting and Exiting the System, see Launch a Windows App Client).

 

5 – Install the Website Certificate

• You have created a website or web application using SMC and the URLs (HTTPs) are available.

• You have not installed the certificate used in the website.

1. Browse the website or web application HTTPs URL in the default browser.

• The Certificate Error: Navigation Blocked page displays due to an untrusted certificate.

2. Click Continue to this website (not recommended).

• In the Desigo CC web page address bar, a Certificate Error security report displays.

3. Click Certificate Error to open a menu that contains a View certificates hyperlink.

4. Click View Certificates.

5. In the Certificate dialog box that displays, click Install Certificate.
   NOTE: The same website/web application certificate (host/self-signed) that was provided during website/web application creation, displays and you can proceed with installing it in the TRCA store. However, in order for the host certificate to work with Windows App client, you must import the root of the host certificate that you used while creating website in the TRCA store.

6. Depending on the type of certificate used, proceed with importing the certificate as follows:

• If the certificate you used while creating a website is a self-signed certificate, then you must install it in the Trusted Root Certification Authorities store.

• If the certificate you used while creating a website is a host certificate, then you must install the root certificate of the host in the Trusted Root Certification Authorities store.

NOTE:
If the Certificate Error: Navigation Blocked page displays, even after installing the website certificate, then verify that the Subject Alternative Name (SAN) property for the selected certificate contains the host name specified while creating the website.
For example, if the website Host name field contains the full computer name, ABCXY022PC.dom01.company.net, then the certificate provided in the Certificate issued to field must contain the full computer name ABCXY022PC.dom01.company.net as one of its names in the SAN property.

 

6 – Install the Web Application Certificate

The certificate you select while creating the web application is the same certificate that you must install in the certificate store under Current User > Trusted Root Certification Authority and Current User > Trusted Publisher certificate before launching the Windows App client. You can do this using the following procedure.

• You have created a web application using SMC and the HTTPs URLs display.

• The Desigo CC web page is open in the browser, and the Desigo CC tab contents are displayed.

1. Do one of the following:

• In the Desigo CC web page, click the Click Here link on the Desigo CC page for a web application.

• In the Desigo CC web page, click the Support tab, and then select the Web Application Certificate link.

2. In the File download – Security Warning dialog box, click Open.

3. In the Certificate dialog box, click Install Certificate.

4. Depending on the type of certificate used, proceed with importing the certificate by doing one of the following:

• If you used a self-signed certificate while creating a web application, then you must install it in the Trusted Root Certification Authorities and Trusted Publisher Windows Certificate store (See Install Certificates in the Trusted Root Certification Authorities (TRCA) Store and Install Certificates in the Trusted Publisher (TP) Store in Web Application Procedures).

• If you used a host certificate while creating a Web Application, then you must install it in the Trusted Publisher Windows Certificate store. You must also install the root certificate of the host in the Trusted Root Certification Authorities store (See Install Certificates in the Trusted Root Certification Authorities (TRCA) Store and Install Certificates in the Trusted Publisher (TP) Store in Web Application Procedures).
  NOTE: If host certificates created with SMC are used for signing the Web Application and the browser is configured to check the publisher's certificate revocation, the Security Warning message may display, even after installing the certificate. In this case, you can either add the website to the Trusted Sites zone to resolve the issue or ignore the warning and click Install (for Windows App client).

 

7 – Launch a Windows App Client

Do this procedure to start Desigo CC as a Windows app client (the client software which is downloaded and installed on demand from a browser).

1. You have installed the security certificate on the computer where you are working with Windows App Client.

2. Launch the Windows browser.

3. In the address bar of the browser, paste the web application URL.

• The Desigo CC page opens in the browser, and the Desigo CC tab contents display.

4. In the Desigo CC tab, click the Windows App Client thumbnail for launching the Windows App Client.

• For browsers IE 11 onwards and Chrome the installation of Desigo CC starts. When completed, the logon dialog box displays.

• For Edge browser, in the Open this file dialog box that displays, click Open.

• For Firefox browser, a warning message displays. Click Advanced.
  
  a. If you have used self-signed certificate while creating a web application, a dialog box displays asking you to Accept risk and Continue.
  
  b. If you have used host certificate while creating a web application, in addition to dialog box Accept risk and Continue.
  

• You need to download the application from downloads.

• Click OK to open the executable file.

• For browsers Firefox and Edge the installation of Desigo CC starts. When completed, the logon dialog box displays.

5. Enter your username and password.

6. Select the domain.

7. Click Logon.

NOTE:
Each time you launch Desigo CC as a Windows App Client, a search for system updates is performed. If a new version of the software is available on the web server (IIS), you can choose to update it or continue using the previous version.