From 2e933dceb591c3505f35c2c1de924f3978fb81a7 Mon Sep 17 00:00:00 2001 From: Niklas Hagman Date: Tue, 19 Nov 2019 15:42:46 +0100 Subject: Transition Keystone admin user to system scope A system-scoped token implies the user has authorization to act on the deployment system. These tokens are useful for interacting with resources that affect the deployment as a whole, or exposes resources that may otherwise violate project or domain isolation. Since Queens, the keystone-manage bootstrap command assigns the admin role to the admin user with system scope, as well as in the admin project. This patch transitions the Keystone admin user from authenticating using project scoped tokens to system scoped tokens. This is a necessary step towards being able to enable the updated oslo policies in services that allow finer grained access to system-level resources and APIs. An etherpad with discussion about the transition to the new oslo service policies is: https://etherpad.opendev.org/p/enabling-system-scope-in-kolla-ansible Change-Id: Ib631e2211682862296cce9ea179f2661c90fa585 Signed-off-by: Niklas Hagman --- tools/init-runonce | 1 - 1 file changed, 1 deletion(-) (limited to 'tools') diff --git a/tools/init-runonce b/tools/init-runonce index b4b873991..f8d7b1c17 100755 --- a/tools/init-runonce +++ b/tools/init-runonce @@ -95,7 +95,6 @@ if [[ $ENABLE_EXT_NET -eq 1 ]]; then fi # Get admin user and tenant IDs -ADMIN_USER_ID=$($KOLLA_OPENSTACK_COMMAND user list | awk '/ admin / {print $2}') ADMIN_PROJECT_ID=$($KOLLA_OPENSTACK_COMMAND project list | awk '/ admin / {print $2}') ADMIN_SEC_GROUP=$($KOLLA_OPENSTACK_COMMAND security group list --project ${ADMIN_PROJECT_ID} | awk '/ default / {print $2}') -- cgit v1.2.3