New Upload weather data from web services into TM1/Planning Analytics — Read the post →

Configuring SSL for PowerConnect

By default the PowerConnect Application Server listens on an unsecure (HTTP) port. It can be configured to serve over a secure (HTTPS) connection instead. The configuration is similar to Using SSL with Arc for TM1, with two PowerConnect-specific differences: the parameter that enables SSL is usessl, and PowerConnect can additionally read an encrypted private key by supplying its password through the pem-passphrase setting.

1. Enable SSL in the configuration file

Open the conf\settings.yml file and set the following parameters in the Web Server Settings section:

Setting

Definition

Value

usessl

Specifies if the web server will listen on a secure (HTTPS) or unsecure (HTTP) port. Set to true to enable SSL.

true

port

The port the web server listens on. When SSL is enabled this is typically changed to the standard HTTPS port.

443

pem-passphrase

Optional. If the key.pem file is protected by a password (i.e. the private key is encrypted), this setting supplies that password so the server can load the key. Leave empty if the key is not encrypted.

""

Example:

2. Provide the certificate files

When SSL is enabled, PowerConnect expects two files in PEM format in the conf\ssl folder of the installation directory:

File

Contents

cert.pem

The server certificate issued by a trusted certificate authority, including the full certificate chain.

key.pem

The private key associated with the certificate.

Copy your cert.pem and key.pem into the conf\ssl folder before starting the service.

note

If the conf\ssl folder does not exist yet, create it inside the installation folder next to conf\settings.yml.

If the conf\ssl folder does not exist yet, create it inside the installation folder next to conf\settings.yml.

If the private key (key.pem) is encrypted with a password, set that same password in the pem-passphrase setting so the server can load the key on startup.

3. Restart and verify

Restart the PowerConnect service for the changes to take effect. Once running, the server can be reached over HTTPS:

You can also confirm the certificate the server is using by calling the admin /certinfo endpoint, which returns the certificate subject, issuer and expiry date.