starlingx/docs
Code Issues Proposed changes
d95c80d36f
docs/doc/source/security/kubernetes/starlingx-rest-api-applications-and-the-web-administration-server.rst
Rafael Jardim d95c80d36f Update Security 
Fixed merge conflict (RS)

Signed-off-by: Rafael Jardim <rafaeljordao.jardim@windriver.com>
Change-Id: I30b882a14196525f440db1108a56bbf862dfaf55
Signed-off-by: Ron Stone <ronald.stone@windriver.com>
2021-04-01 16:02:36 -04:00

1.3 KiB
Raw Blame History

StarlingX REST API Applications and the Web Administration Server

provides support for secure HTTPS external connections used for StarlingX REST API application endpoints (Keystone, Barbican and StarlingX) and the web administration server.

By default HTTPS access to StarlingX REST and Web Server's endpoints are disabled; i.e. accessible via HTTP only.

For secure HTTPS access, an x509 certificate and key is required. When HTTPS is enabled for the first time on a system, a self-signed certificate and key are automatically generated and installed for the StarlingX REST and Web Server endpoints.

Note

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

For secure remote access, an intermediate or Root -signed certificate and key are required. The use of a Root -signed certificate is strongly recommended.

You can update the certificate used for HTTPS access at any time.