forked from openstack/barbican
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Implement secure RBAC for orders API
Add new project scope specific RBAC rules for the orders API. The old rules still apply, but eventually will be deprecated. The new rules do include some changes to default policy, which are documented in the release note. Change-Id: I8e6963d7ab788038102c7f4570b3f2c9a342eabf
- Loading branch information
Showing
2 changed files
with
26 additions
and
10 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
15 changes: 15 additions & 0 deletions
15
releasenotes/notes/secure-rbac-order-policy-2068c64cb6830c6c.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
--- | ||
features: | ||
- | | ||
Implement secure-rbac for orders resource. | ||
security: | ||
- | | ||
The current policy allows all users except those with the audit role to | ||
list orders or retrieve an orders metadata. The new desired policy will | ||
restrict this to members. For backwards compatibility, the old policies | ||
remain in effect, but they are deprecated and will be removed in future, | ||
leaving the more restrictive new policy. | ||
- | | ||
The new secure-rbac policy allows for secret deletion by members. This is | ||
a change from the previous policy that only allowed deletion by the | ||
project admin. |