Merge "Update the "http" to "https""

This commit is contained in:
Jenkins 2017-04-22 02:30:30 +00:00 committed by Gerrit Code Review
commit 53b8a24e43
1 changed files with 4 additions and 4 deletions

View File

@ -53,18 +53,18 @@ Key management access control
Special privileges can be assigned on behalf of an end user to allow
them to manage their own encryption keys, which are required when
creating the encrypted volumes. The Barbican `Default Policy
<http://docs.openstack.org/developer/barbican/admin-guide-cloud/access_control.html#default-policy>`_
<https://docs.openstack.org/developer/barbican/admin-guide-cloud/access_control.html#default-policy>`_
for access control specifies that only users with an ``admin`` or
``creator`` role can create keys. The policy is very flexible and
can be modified.
To assign the ``creator`` role, the admin must know the user ID,
project ID, and creator role ID. See `Assign a role
<http://docs.openstack.org/admin-guide/cli-manage-projects-users-and-roles.html#assign-a-role>`_
<https://docs.openstack.org/admin-guide/cli-manage-projects-users-and-roles.html#assign-a-role>`_
for more information. An admin can list existing roles and associated
IDs using the ``openstack role list`` command. If the creator
role does not exist, the admin can `create the role
<http://docs.openstack.org/admin-guide/cli-manage-projects-users-and-roles.html#create-a-role>`_.
<https://docs.openstack.org/admin-guide/cli-manage-projects-users-and-roles.html#create-a-role>`_.
Create an encrypted volume type
@ -152,7 +152,7 @@ the creator role in the following way:
For details, see the
`Barbican Access Control page
<http://docs.openstack.org/developer/barbican/admin-guide-cloud/access_control.html>`_.
<https://docs.openstack.org/developer/barbican/admin-guide-cloud/access_control.html>`_.
.. note::