https://bugs.launchpad.net/glance/+bug/1620833
Would be my suggestion for a conservative / quick-hit / high impact bug to
consider for inclusion. Especially since this cycle is when the
documentation for using db.simple was added, it seems like it¹d be nice if
this were also fixed.
Tim
On 9/2
Hi Kam,
The first thing I'd do is ensure that you're editing the correct "in use"
policy file ( /etc/keystone/policy.json , if it's a default devstack install ).
Secondly, a good test would be to change the actual policy to "!" (deny all).
If that still allows anyone but the service token to do
Thanks for asking this, I would also like to know what the “real” answer is.
But what I’ve found myself doing recently, since it was unwise to 100% count on
rejoin-stack.sh, was to “do” everything via scripts and take periodic backups
of same. You’re still only one power outage away from losing
We are running keystone kilo in production, and I¹m actively implementing
RBAC right now. I¹m certain that, at least with the version of keystone
we¹re running, a restart is NOT required when the policy file is modified.
Tim
On 12/9/15, 9:18 AM, "Edgar Magana" wrote:
>We use RBAC in producti