Now that we have system scope in place, we should make sure at least
one user has a role assignment on the system. We can do this at the
same time we grant the user a role on a project during bootstrap.
This is backwards compatible because even if a deployment doesn't use
system-scope, the assignment will just sit there. The deployment will
have to opt into enforcing scope by updating configuration options
for oslo.policy to enforce scoping.
This shouldn't prevent deployments from fixing bug 968696 and using
system scope.
Closes-Bug: 1749268
Change-Id: I6b7196a28867d9a699716c8fef2609d608a5b2a2
(cherry picked from commit 3c524e6491c1b35a2f8413ebe046c238bf530d71)
Reviewed: https:/ /review. openstack. org/544097 /git.openstack. org/cgit/ openstack/ keystone/ commit/ ?id=ddd7ff300e9 159899f27a27fb3 dda8ef9b91be1f
Committed: https:/
Submitter: Zuul
Branch: stable/queens
commit ddd7ff300e91598 99f27a27fb3dda8 ef9b91be1f
Author: Lance Bragstad <email address hidden>
Date: Thu Dec 28 22:11:32 2017 +0000
Grant admin a role on the system during bootstrap
Now that we have system scope in place, we should make sure at least
one user has a role assignment on the system. We can do this at the
same time we grant the user a role on a project during bootstrap.
This is backwards compatible because even if a deployment doesn't use
system-scope, the assignment will just sit there. The deployment will
have to opt into enforcing scope by updating configuration options
for oslo.policy to enforce scoping.
This shouldn't prevent deployments from fixing bug 968696 and using
system scope.
Closes-Bug: 1749268
Change-Id: I6b7196a28867d9 a699716c8fef260 9d608a5b2a2 a2f8413ebe046c2 38bf530d71)
(cherry picked from commit 3c524e6491c1b35