StarlingX REST API Applications and the Web Administration Server Certificate

Note

This procedure is deprecated. For up-to-date information, refer to: Create a local CA Issuer.

By default, StarlingX provides HTTP access to REST API application endpoints (Keystone, Barbican and StarlingX) and the web administration server. For improved security, you can enable HTTPS access. When HTTPS access is enabled, HTTP access is disabled.

When HTTPS is enabled for the first time on a StarlingX system, a self-signed server certificate and key are automatically generated and installed for REST and Web Server endpoints. In order to connect, remote clients must be configured to accept the self-signed server certificate without verifying it. This is called insecure mode.

For secure-mode connections, an Intermediate or Root CA-signed server certificate and key are required. The use of an Intermediate or Root CA-signed server certificate is strongly recommended. Refer to the documentation for the external Intermediate or Root CA that you are using, on how to create public certificate and private key pairs, signed by an Intermediate or Root CA, for HTTPS.

Note

Refer to the documentation for the external Intermediate or Root CA that you are using, on how to create public certificate and private key pairs, signed by an Intermediate or Root CA, for HTTPS.

You can update the certificate and key used by StarlingX for the REST and Web Server endpoints at any time after installation.

For additional security, StarlingX optionally supports storing the private key of the StarlingX REST and Web Server certificate in a TPM hardware device. TPM 2.0-compliant hardware must be available on the controller hosts.

For more details, refer to:

• Enable HTTPS Access for StarlingX REST and Web Server Endpoints
• Install/Update the StarlingX Rest and Web Server Certificate
• Secure StarlingX REST and Web Certificate’s Private Key Storage with TPM