Arun Kant ce6336f393 User with creator role can delete his/her own secret and container ... Modified policy and tests to verify this change. As per this change, user with 'creator' role can delete a secret or a container as long as that user has initially created that secret or container. There is still a difference between 'admin' role and 'creator' role behavior around delete operation. With this change, users with 'creator' role cannot delete any other user's secret/container in same project while user with 'admin' role can do that. Updated role docs to reflect this behavior. Change-Id: I53e5529ed34ac4acc76348ca0431cb3de7934b6d		2016-07-25 13:42:01 -07:00
..
vassals	Remove deprecated references to admin endpoint.	2015-05-04 15:12:12 -05:00
api_audit_map.conf	Adding auditing support for API request using audit middleware	2016-01-21 09:32:39 -08:00
barbican-api-paste.ini	Don't supply auth_token information by default in paste	2016-06-09 09:57:43 +10:00
barbican-functional.conf	User with creator role can delete his/her own secret and container	2016-07-25 13:42:01 -07:00
barbican.conf	Move rabbit configurations to oslo_messaging_rabbit section	2016-07-11 15:46:28 +08:00
policy.json	User with creator role can delete his/her own secret and container	2016-07-25 13:42:01 -07:00