Age | Commit message (Collapse) | Author | Files | Lines |
|
Use the "keystone-manage bootstrap" command to instead of admin_token.
Because the admin_token is treated as a "shared secret" that can be used
to bootstrap Keystone through the API. This "token" does not represent a
user (it has no identity), and carries no explicit authorization (it
effectively bypasses most authorization checks).
Use the API v3 to instead of API v2.0. Identity API v3 was established to
introduce namespacing for users and projects by using "domains" as a
higher-level container for more flexible identity management and fixed a
security issue in the v2.0 API (bearer tokens appearing in URLs).
JIRA: COMPASS-491
Change-Id: I56182c14b761728c3492b9dd2b05c3b57aa5f35f
Signed-off-by: liyuenan <liyuenan@huawei.com>
|
|
JIRA: COMPASS-423
Change-Id: I3efa0868c0147cc43b1df096ae89a6bdc42f4204
Signed-off-by: Yifei Xue <xueyifei@huawei.com>
|
|
JIRA: COMPASS-372
Change-Id: I869e5b29e87de06dd6116c4f4f8b5735fa231e64
Signed-off-by: Yifei Xue <xueyifei@huawei.com>
|
|
JIRA: COMPASS-339
only ubuntu supported currently
Change-Id: I14bae2b11a811c1131eba1d25f57783dffbb0b51
Signed-off-by: Yifei Xue <xueyifei@huawei.com>
|