3143d86b69
Updates for patchset 2 review comments Changed link depth of main Planning index and added some narrative guidance Added planning/openstack as sibling of planning/kubernetes Related additions to abbrevs.txt Added max-workers substitution to accomodate StarlingX/vendor variants Signed-off-by: Ron Stone <ronald.stone@windriver.com> Change-Id: Ibff9af74ab3f2c00958eff0e33c91465f1dab6b4 Signed-off-by: Stone <ronald.stone@windriver.com>
30 lines
1018 B
ReStructuredText
Executable File
30 lines
1018 B
ReStructuredText
Executable File
|
|
.. iym1475074530218
|
|
.. _https-access-planning:
|
|
|
|
=====================
|
|
HTTPS Access Planning
|
|
=====================
|
|
|
|
You can enable secure HTTPS access for |prod-os|'s REST API endpoints or
|
|
OpenStack Horizon Web interface users.
|
|
|
|
.. note::
|
|
To enable HTTPS access for |prod-os|, you must enable HTTPS in the
|
|
underlying |prod-long| platform.
|
|
|
|
By default, |prod-os| provides HTTP access for remote connections. 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 |prod-os| system, a self-signed
|
|
certificate is automatically installed. In order to connect, remote clients
|
|
must be configured to accept the self-signed certificate without verifying it
|
|
\("insecure" mode\).
|
|
|
|
For secure-mode connections, a |CA|-signed certificate is required. The use of
|
|
a |CA|-signed certificate is strongly recommended.
|
|
|
|
You can update the certificate used by |prod-os| at any time after
|
|
installation.
|