Add a certificate
for a secure HTTP (HTTPS) gadget to allow the gadget to load into the Finesse
desktop and successfully perform HTTPS requests to the Finesse server.
This process
allows HTTPS communication between the Finesse gadget container and the
third-party gadget site for loading the gadget and performing any API calls
that the gadget makes to the third-party server.
Note |
A gadget that
loads using HTTPS may still use HTTP communication between that gadget and the
application server where it resides. If all traffic must be secure, the gadget
developer must ensure that HTTPS is used to make API calls to the application
server.
|
The certificate
must be signed with a common name. The gadget URL in the desktop layout must
use the same name (whether it uses an IP address or a fully qualified domain
name) as the name with which the certificate is signed. If the certificate name
and the name in the gadget URL do not match, the connection is not trusted and
the gadget does not load.
To find the
certificate name, enter the gadget URL in your browser. Click the lock icon in
the address bar and then click View Details. Look for the common name field.
The Finesse host
must be able to resolve this name using the DNS host that was entered during
installation. To verify that Finesse can resolve the name, run the CLI command
"utils network
ping <hostname>".