SmartSignal* Web Services

Installation Guide

© 2022 General Electric Company

Contents

Chapter 1: Introduction 1
Introduction 2

Chapter 2: Prerequisites 3
Prerequisites for Web Services Server 4

Chapter 3: Installation Steps 9

Web Services Installation Steps (Execute as SmartSignal Services Account) 10

Chapter 4: Upgrade 16
Web Services Upgrade Steps (Execute as SmartSignal Services Account) 17

Chapter 5: Troubleshooting 22
Troubleshooting 23

ii SmartSignal* Web Services Installation Guide

Copyright GE Digital
Disclaimer of Warranties and Liability
The information contained in this manual is believed to be accurate and reliable. However, GE Digital
assumes no responsibilities for any errors, omissions or inaccuracies whatsoever. Without limiting the
foregoing, GE Digital disclaims any and all warranties, expressed or implied, including the warranty of
merchantability and fitness for a particular purpose, with respect to the information contained in this
manual and the equipment or software described herein. The entire risk as to the quality and
performance of such information, equipment and software, is upon the buyer or user. GE Digital shall not
be liable for any damages, including special or consequential damages, arising out of the use of such
information, equipment and software, even if GE Digital has been advised in advance of the possibility of
such damages. The use of the information contained in the manual and the software described herein is
subject to GE Digital standard license agreement, which must be accepted by the buyer or user before the
use of such information, equipment or software.

Trademark Notices
© 2022, General Electric Company. All rights reserved.

SmartSignal is a trademark of GE Digital, a wholly-owned subsidiary of General Electric Company.

* Indicates a trademark of General Electric Company and/or its subsidiaries.
All other product names and marks identified throughout this book are trademarks or registered
trademarks of their respective companies. They are used throughout this book in editorial fashion only. No
such use, or the use of any trade name, is intended to convey endorsement or affiliation.
No part of this publication may be reproduced in any form, or stored in a database or retrieval system, or
transmitted or distributed in any form by any means, electronic, mechanical photocopying, recording or
otherwise, without the prior written permission of GE Digital. Information contained herein is subject to
change without notice.

© 2022 General Electric Company iii

 Chapter

1
Introduction
Topics:

• Introduction

© 2022 General Electric Company 1

Introduction
Installation must occur after the SmartSignal Database has been created or upgraded. During the
installation of Web Services, we require elevation of privileges:
• SQL Server user with sysadmin privileges to the SmartSignal database
• SmartSignal Services Account with admin privileges to the Web Services server. After installation, the
SmartSignal Services Account privileges return to domain or local user.
• Web Services cannot coexist on the same server with previous versions.
• Web Services should be installed on a separate Web Server and cannot be installed across servers.
• Installation supports both default and user created web sites.

2 © 2022 General Electric Company

 Chapter

2
Prerequisites
Topics:

• Prerequisites for Web Services

Server

© 2022 General Electric Company 3

Prerequisites for Web Services Server
Requirement Description

Operating System Microsoft Windows Server 2019, 2016 or 2012 R2 64-Bit with
latest Service Pack

CPU 2 Quad Core, 2.6 GHz or faster

RAM 4 GB or more

Disk Space 1 GB free

Software • IIS (included in your operating system)

• .NET Framework 4.8
• MSOLEDB 18.5.0 or higher
• ASP .NET 4.8
• .Net Core 3.1.x Hosting bundle (.Net Core Runtime 3.1.x +
ASP.NET Core Runtime 3.1.x + IIS support)
• Application Request Routing (ARR)
• URL - Rewrite Component
• Redis Cache
• nodejs
• npm
• PM2

Setup • Web Services

• Customer supplied SSL certificate

Ports • SmartSignal Alert UI Localhost Port: 3004 (http)

• SmartSignal App Hub Localhost Port: 3000 (http)
• SmartSIgnal Case UI Localhost Port: 3002 (http)
• SmartSignal Chart UI Localhost Port: 9042 (http)
• SmartSignal Rest Service Port: 5000 (http)
• SmartSignal Uaa Service Port: 10443 (https)
• SmartSignal Web Service Port: 443 (https)

Setup:
Confirm that the SmartSignal Services Account has local Administrator rights to the server hosting
the Web Services and Administrator privileges to the SmartSignal database (required only for
installation).
1. For Windows 2012 Server Only - Install Visual C++ Redistributables for Visual Studio 2015
2. Download and install MSOLEDB 18.5.0 or higher
https://docs.microsoft.com/en-us/sql/connect/oledb/release-notes-for-oledb-driver-for-sql-server?
view=sql-server-ver15#1863
3. Download and install .Net Core 3.1.x Hosting bundle (.Net Core Runtime 3.1.x + ASP.NET Core
Runtime 3.1.x + IIS support) as administrator
https://dotnet.microsoft.com/download/dotnet-core/thank-you/runtime-aspnetcore-3.1.4-windows-
hosting-bundle-installer

4 © 2022 General Electric Company

 4. Download and install Redis Cache
https://redis.io/download
5. Download and install Node.js 64-bit
https://nodejs.org/en/download/
Select all the default settings.
6. Install and configure PM2 using the delivered pm2-4.5.6-npm_cache.zip file.
7. Create a new folder C:\temp
8. Extract the pm2-4.5.6-npm_cache.zip file into C:\temp folder. A subfolder C:\temp\.npm_
cache will be created.

9. Navigate to C:\temp, using an Administrator Command Prompt

> npm install --global --offline --cache .\.npm_cache --shrinkwrap

false --loglevel=error --no-audit --no-fund pm2
10. Copy the pm2-windows-service-0.2.1.tgz to the Temp folder
11. Confirm PM2 installed using an Administrator Command Prompt

> pm2 list

12. Install SmartSignal PM2 Service using the delivered pm2-windows-service-0.2.1.tgz as a

SmartSignal Services Account. Open the command prompt with Administrative Privileges and use the
following command:

>npm install -g pm2-windows-service-0.2.1.tgz

© 2022 General Electric Company 5

 13. Configure SmartSignal PM2 Service using the same Command Prompt with Administrative
Privileges with the following command.

> pm2-service-install -n SmartSignal_PM2

PM2 will prompt the following:

• Perform environment setup (recommended)? Y
• Set PM2_HOME? Y
• PM2_HOME value (this path should be accessible to the service user and should not contain any
"user-context" variables [e.g. %APPDATA%]): %APPDATA%
• Set PM2_SERVICE_SCRIPTS (the list of start-up scripts for pm2)? Y
• Set the list of startup scripts/files (semi-colon separated json config files or js files)
• Set PM2_SERVICE_PM2_DIR (the location of the global pm2 to use with the service)?
[recommended] Y
• Specify the directory containing the pm2 version to be used by the service, Enter C:\USERS
\<User>\APPDATA\ROAMING\NPM\node_modules\pm2\index.js

14. Configure the SmartSignal PM2 Service to use SmartSignal Services Account
a. Open the Windows Services dialog box.
b. In the services list, select the SmartSignal_PM2 service.
c. Right-click on the SmartSignal_PM2 service and select Properties.
d. Select the Log On tab.
e. Select This Account radio button, and enter the user ID and password details for the SmartSignal
Services Account that the service is to run under.
f. Select OK.
g. Start the SmartSignal_PM2 service.
15. Confirm PM2 running using an Administrator Command Prompt

>pm2 list

16. Download and Install Application Request Routing 3.0 (ARR) x64 installer
https://www.iis.net/downloads/microsoft/application-request-routing
17. Run IISReset to restart IIS.

6 © 2022 General Electric Company

 18. Navigate to IIS Manager and select Application Request Routing. Select Server Proxy Settings

19. Enable proxy

20. Uncheck the Reverse rewrite host in response headers If you do this at the machine level, it'll take
effect for all sites. If you do it on a particular site, it'll only take effect for that site, and other sites on
the box will be unaffected.
21. Select Apply
22. Install url-rewrite component in IIS. https://www.iis.net/downloads/microsoft/url-rewrite
23. Acquire SSL certficate (.cer or .pfx) before Installing Web Services (Website will not be
reachable without SSL certificate).
Refer to, How to obtain SSL Certificate.
24. Validate your certificate:
a. In the powershell window, run the following command, replacing your certificate path and name:

Get-PfxCertificate C:\CertPath\my.cer | Select-Object *

b. Enter your certificate password.
c. If the certificate is valid, the following window is displayed:

Disable Windows Authentication:

1. On the taskbar, select Server Manager.
2. In the Server Manager window, select Manage, and then select Remove Roles and Features.
3. In the Server Roles window, expand Web Server (IIS), Web Server, and then select Security.

© 2022 General Electric Company 7

 4. Confirm that the Windows Authentication check box is disabled.

5. Select Next.
6. In the Select Features page, select Next.
7. In the Confirm Removal Selections page, select Remove.
8. In the Results page, select Close.

8 © 2022 General Electric Company

 Chapter

3
Installation Steps
Topics:

• Web Services Installation Steps

(Execute as SmartSignal
Services Account)

© 2022 General Electric Company 9

Web Services Installation Steps (Execute as SmartSignal
Services Account)
Procedure
1. Execute GE SmartSignal Sentinel Web installer setup.exe as administrator. The wizard will
walk you through a series of standard product installation dialogs. Select Next to proceed and then
select Install.

Figure 1: SmartSignal Web Services: Change Destination Dialog

2. Choose the default location or navigate to another Destination Folder and select Next.

Figure 2: SmartSignal Web Services: Services Account Logon Dialog

10 © 2022 General Electric Company

 3. Enter the SmartSignal Services account information that will be used to anonymously access the
SmartSignal Web Services on (IIS).
• SmartSignal Services Account: Enter Domain\Domain User or <Local>Machine
\<Local>MachineUser that was specified when the SmartSignal database was installed or
upgraded.
• Password: Enter SmartSignal Services account password.

Figure 3: SmartSignal Web Services: Redis Logon Dialog

4. Enter the Redis Logon information
• Host: Enter your Redis Host name.
• User Name: Enter your Redis user name; User name can be blank.
• Password: Enter your Redis password; Password can be blank.

Figure 4: SmartSignal Web Services: SmartSignal Database Dialog

© 2022 General Electric Company 11

 5. Enter the SmartSignal Database information
• Database server that you are installing to: Browse to the name of the server hosting the
SmartSignal SQL Server database and dedicated instance name.
• Name of database catalog: Browse to your SmartSignal database.

Figure 5: SmartSignal Web Services: SmartSignal Web Services Dialog

6. Enter the SmartSignal Web Services information
• Web Site URL: Enter your Web Site URL, i.e. www.costo.com.
• SSL Certificate Path: Browse to your SSL certificate.
• SSL Certificate Password: Enter your SSL certificate password.
7. Select the security certificate file (.cer or .pfx) that you want to install.
Note: The SSL certificate is also installed when the website and the virtual directories are installed.
• SmartSignal Web Service Port: 443
• SmartSignal Rest Service Port: 5000
• SmartSignal Uaa Service Port: 10443

12 © 2022 General Electric Company

 Figure 6: SmartSignal Web Services: SmartSignal Ready to Install Dialog
8. Select Install. To start the installation of Web Services.
9. Select Finish to allow background command window process to complete.
10. Open the Administrator Command Prompt and navigate to the location C:\temp\Install.
11. Enter the following command to display the application status in PM2:

> pm2 list

If alert-UI, app-hub, case-UI and charts-UI are not listed or online, enter the following commands in
the Administrator Command prompt:

>cd <Program Files>\SmartSignal\SmartSignal Web Services\

> powershell.exe -file Service_Start.ps1

12. Display the application status in PM2, using an Administrator Command prompt.

> pm2 list

If status is not online, restart SmartSignal_PM2 service

© 2022 General Electric Company 13

 13. Open the Administrator Command Prompt and navigate to the location C:\temp\Install.
14. Enter the following command to display the application status in PM2, using an elevated command
prompt as the service account user.

> pm2 list

15. Confirm certificate binds with web app.

‘SmartSignal Reverse Proxy Services’ and ‘SmartSignal UAA Services’ should bind to certificate, as
displayed below.
Host name should be identical to SSL Certificate.

If SSL certificate is empty or assigned to a wrong certificate, you need select the right certificate and
save the change.
16. Test your Web Services Connection.
a) Open a Web Browser.
b) Enter the URL that you entered during the install, as https://<Your.URL.Here>
c) At the login prompt, enter the SmartSignal user account credentials, this may be the default Admin
account if no users have been created.

14 © 2022 General Electric Company

 Note:
Web Services Logs:
C:\ProgramData\SmartSignal\WebServices\Logs\restfulservice.log
C:\ProgramData\SmartSignal\WebServices\Logs\uaaservice.log

© 2022 General Electric Company 15

 Chapter

4
Upgrade
Topics:

• Web Services Upgrade Steps

(Execute as SmartSignal
Services Account)

16 © 2022 General Electric Company

Web Services Upgrade Steps (Execute as SmartSignal Services
Account)

Procedure
1. Stop the SmartSignal_PM2 service.
2. Use an elevated command prompt as the service account user, and execute the following
command:

><Program Files>\SmartSignal\SmartSignal Web Services

\Service_Delete.bat
3. Uninstall Web Services from Program and Features.
4. Start the SmartSignal_PM2 service.
5. Execute GE SmartSignal Sentinel Web installer setup.exe as administrator. The wizard will
walk you through a series of standard product installation dialogs. Select Next to proceed and then
Install.

Figure 7: SmartSignal Web Services: Change Destination Dialog

6. Choose the default location or navigate to another Destination Folder and select Next.
7. Enter the SmartSignal Services account information that will be used to anonymously access the
SmartSignal Web Services on (IIS).

© 2022 General Electric Company 17

 Figure 8: SmartSignal Web Services: Services Account Logon Dialog

• SmartSignal Services Account: Enter Domain\Domain User or <Local>Machine

\<Local>MachineUser that was specified when the SmartSignal database was installed or
upgraded.
• Password: Enter SmartSignal Services account password.
8. Enter the Redis Logon information.

Figure 9: SmartSignal Web Services: Redis Logon Dialog

• Host: Enter your Redis Host name.

• User Name: Enter your Redis user name; User name can be blank.
• Password: Enter your Redis password; Password can be blank.
9. Enter the SmartSignal Database information.

18 © 2022 General Electric Company

 Figure 10: SmartSignal Web Services: SmartSignal Database Dialog

• Database server that you are installing to: Browse to the name of the server hosting the
SmartSignal SQL Server database and dedicated instance name.
• Name of database catalog: Browse to your SmartSignal database.
10. Enter the SmartSignal Web Services information

Figure 11: SmartSignal Web Services: SmartSignal Web Services Dialog

• Web Site URL: Enter your Web Site URL, i.e. www.costo.com.
• SSL Certificate Path: Browse to your SSL certificate.
• SSL Certificate Password: Enter your SSL certificate password.
11. Select the security certificate file (.cer or .pfx) that you want to install.
Note: The SSL certificate is also installed when the website and the virtual directories are installed.

© 2022 General Electric Company 19

 • SmartSignal Web Service Port: 443
• SmartSignal Rest Service Port: 5000
• SmartSignal Uaa Service Port: 10443
12. Select Install to start the installation of Web Services.

Figure 12: SmartSignal Web Services: SmartSignal Ready to Install Dialog

13. Select Finish to allow background command window process to complete.
14. Open the Administrator Command Prompt and navigate to the location C:\temp\Install.
15. Enter the following command to display the application status in PM2:

> pm2 list

If alert-UI, app-hub, case-UI and charts-UI are not listed or online, then enter the following commands
in the Administrator Command Prompt:

>cd <Program Files>\SmartSignal\SmartSignal Web Services\

> powershell.exe -file Service_Start.ps1

20 © 2022 General Electric Company

 16. Display application status in PM2, using an Administrator Command prompt.

> pm2 list

If status is not online, restart the SmartSignal_PM2 service

Execute to validate

> pm2 list

17. Confirm certificate binds with web app

‘SmartSignal Reverse Proxy Services’ and ‘SmartSignal UAA Services’ should bind to certificate.
Host name should be identical to SSL Certificate.

If SSL certificate is empty or assigned to an incorrect certificate, update the correct certificate and
save the change.
18. Restart IIS.
19. Test the Web Services Connection.
Open a Web Browser
Enter the URL that you entered during the install, as https://<Your.URL.Here>
20. At the login prompt, enter the SmartSignal user account credentials, this may be the default Admin
account if no users have been created.
Note:
Web Services Logs:
C:\ProgramData\SmartSignal\WebServices\Logs\restfulservice.log
C:\ProgramData\SmartSignal\WebServices\Logs\uaaservice.log

© 2022 General Electric Company 21

 Chapter

5
Troubleshooting
Topics:

• Troubleshooting

22 © 2022 General Electric Company

Troubleshooting
• Sentinel Lite portal URL return 403 forbidden - The Web server is configured to not list the
contents of directory

Issue: The inbound rule for the reverse proxy is lost.

Reverse proxy rules are stored in web.config file of physical path of reverse proxy site.
If web.config is missing, rule is lost.
Recover: Reconfigure the rule.
• 502 web server proxy issue
Issue: Port 3000 is not accessible, PM2 or AppHUB isn't started. Please check PM2 or AppHub status.
• 503 service unavailable
Issue: Wrong application pool user caused application pool to stop.
• Logon fail and 401 error in APPHub

Issue: If bearer token is still in session of UAA , AppHUB failed to communicate with UAA service.
Check:
◦ The UAA URL in UAA service and AppHUB are same (case sensitive).
◦ AppHUB can access the UAA from UAA URL.
If UAA URL is a public web domain URL, because of the security setting, the public domain URL cannot
be resolved. We need set the IP and public web domain URL mapping in /etc/host file.
Issue: If bearer token is not in session of UAA , it implies that the AppHUB has taken the bearer token,
but failed to validate the token by public key.
Check:

© 2022 General Electric Company 23

 ◦ The UAA URL in UAA service and AppHUB are same (case sensitive).
◦ AppHUB fail to grab public RSA key or public RSA key is incorrect
• Sample Reverse proxy configuration

24 © 2022 General Electric Company

 Rule Web Scaler Configuration

Inbound rule 1 against URL Reverser Proxy1 (https://ReverseProxyUrl:443)

Regular Expression:
from: (.*)
to: https://ReverseProxyUrl/{R:1}

<conditions
logicalGrouping="MatchAll">
<add input="{REQUEST_URI}"
pattern="/login.do"
negate="true" />
<add input="{REQUEST_URI}"
pattern="/oauth/token"
negate="true" />
<add input="{REQUEST_URI}"
pattern="/token_key"
negate="true" />
<add input="{REQUEST_URI}"
pattern="/logout"
negate="true" />
<add input="{REQUEST_URI}"
pattern="/appHubConfig"
negate="true" />
<add input="{REQUEST_URI}"
pattern="^/login$"
negate="true" />
<add input="{REQUEST_URI}"
pattern="/oauth/authorize"
negate="true" />
<add input="{REQUEST_URI}"
pattern="/resources"
negate="true" />
<add input="{REQUEST_URI}"
pattern="/logout\?redirect"
negate="true" />
</conditions>

For Example:
https://ReverseProxyUrl/login?state=/
should be converted to
https://ss-web-url/login?state=/

© 2022 General Electric Company 25

 Rule Web Scaler Configuration

Inbound rule 2 Regular Expression:

from: (.*)
to: : https://ReverseProxyUrl/{R:1}

<conditions
logicalGrouping="MatchAny">
<add input="{REQUEST_URI}"
pattern="/login.do" />
<add input="{REQUEST_URI}"
pattern="/oauth/token" />
<add input="{REQUEST_URI}"
pattern="/token_key" />
<add input="{REQUEST_URI}"
pattern="/appHubConfig" />
<add input="{REQUEST_URI}"
pattern="^/login$" />
<add input="{REQUEST_URI}"
pattern="/oauth/authorize" />
<add input="{REQUEST_URI}"
pattern="/resources" />
<add input="{REQUEST_URI}"
pattern="/logout\?redirect" />
</conditions>
</conditions>

For Example:
https://ReverseProxyUrl/login?state=/
should be converted to
https://ss-web-url/login?state=/

26 © 2022 General Electric Company

 Rule Web Scaler Configuration

Outbound rule 1 against HTTP Status 302 and Regular Expression:

RESPONSE_Location
from: https(.*)ss-web-url:10443(.*)
to: https{R:1}ReverseProxyUrl:10443{R:2}
For Example:
https://ss-web-url:10443/oauth/authorize?
response_type=code&redirect_uri=https://ss-web-url/
callback&state=/&client_id=webapp.496bb641-78b5-4a18-
b1b7-fde29788db38.991e5c23-3e9c-4944-
b08b-9e83ef0ab598
should be converted to
https://ReverseProxyUrl:10443/oauth/authorize?
response_type=code&redirect_uri=https://ss-web-url/
callback&state=/&client_id=webapp.496bb641-78b5-4a18-
b1b7-fde29788db38.991e5c23-3e9c-4944-
b08b-9e83ef0ab598
After replacing the initial part of the URL: ss-web-url

Outbound rule 2 against HTTP Status 302 and Regular Expression:

RESPONSE_Location
from: https(.*)ss-web-url(.*)callback(.*)code=(.*)
to : https{R:1}ReverseProxyUrl{R:2}callback{R:3}code={R:4}
For Example:
https://ss-web-url/callback?code=6e1879b9-69a2-48f7-
b712-71dc9780a4ac&state=/allback?code=94beb334-
a5e4-4bdc-a51b-c6628137a805&state=/
should be converted to
https://ReverseProxyUrl/callback?
code=6e1879b9-69a2-48f7-b712-71dc9780a4ac&state=/
callback?code=94beb334-a5e4-4bdc-a51b-
c6628137a805&state=/

IIS Proxy Configuration File:

<?xml version="1.0" encoding="UTF-8"?>

<configuration>
<system.webServer>
<rewrite>
<rules>
<rule name="RedirectAppHubCall">
<match url="(.*)" />
<conditions logicalGrouping="MatchAll">
<add input="{REQUEST_URI}" pattern="/login.do"
negate="true" />
<add input="{REQUEST_URI}" pattern="/oauth/
token" negate="true" />
<add input="{REQUEST_URI}" pattern="/
token_key" negate="true" />
<add input="{REQUEST_URI}" pattern="/
appHubConfig" negate="true" />
<add input="{REQUEST_URI}" pattern="^/login$"
negate="true" />
<add input="{REQUEST_URI}" pattern="/oauth/
authorize" negate="true" />
<add input="{REQUEST_URI}" pattern="/
resources" negate="true" />
<add input="{REQUEST_URI}" pattern="/logout\?
redirect" negate="true" />

© 2022 General Electric Company 27

 </conditions>
<action type="Rewrite" url="https://dv-sl-
deploy.nms.dev.ps.ge.com/{R:1}" logRewrittenUrl="true" />
</rule>
<rule name="RedirectUaaCall">
<match url="(.*)" />
<conditions logicalGrouping="MatchAny">
<add input="{REQUEST_URI}" pattern="/
login.do" />
<add input="{REQUEST_URI}" pattern="/oauth/
token" />
<add input="{REQUEST_URI}" pattern="/
token_key" />
<add input="{REQUEST_URI}" pattern="/
appHubConfig" />
<add input="{REQUEST_URI}" pattern="^/login
$" />
<add input="{REQUEST_URI}" pattern="/oauth/
authorize" />
<add input="{REQUEST_URI}" pattern="/
resources" />
<add input="{REQUEST_URI}" pattern="/logout\?
redirect" />
</conditions>
<action type="Rewrite" url="https://dv-sl-
deploy.nms.dev.ps.ge.com:10443/{R:1}" logRewrittenUrl="true" />
</rule>
</rules>
<outboundRules>
<rule name="Outbound4AppHub"
preCondition="isRedirection" patternSyntax="ECMAScript">
<match serverVariable="RESPONSE_Location"
pattern="https(.*)dv-sl-deploy.nms.dev.ps.ge.com:10443(.*)" />
<action type="Rewrite" value="https{R:1}dv-sent-
lte-iis.nms.dev.ps.ge.com{R:2}" />
</rule>
<rule name="OutboundRule4UAA"
preCondition="isRedirection" patternSyntax="ECMAScript">
<match serverVariable="RESPONSE_Location"
pattern="https(.*)dv-sl-
deploy.nms.dev.ps.ge.com(.*)callback(.*)code=(.*)" />
<action type="Rewrite" value="https{R:1}dv-sent-
lte-iis.nms.dev.ps.ge.com{R:2}callback{R:3}code={R:4}" />
</rule>
<preConditions>
<preCondition name="isRedirection">
<add input="{RESPONSE_STATUS}" pattern="302" />
</preCondition>
</preConditions>
</outboundRules>
</rewrite>
</system.webServer>
</configuration>

For localhost, the loopback name resolution is handled within DNS itself.

28 © 2022 General Electric Company

 Confirm certificate bind with web app
Open IIS Manager, user should see 3 apps.

SmartSignal Reverse Proxy Services’ and ‘SmartSignal UAA Services’ should bind to certificate, as
displayed below.

If SSL certificate is not assigned, you should select the right certificate and save the change.

© 2022 General Electric Company 29