barbican/etc
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
..
barbican User with creator role can delete his/her own secret and container 2016-07-25 13:42:01 -07:00
init Change naming convention for Barbican config files 2015-06-09 11:04:56 -05:00
logrotate.d Added barbican-api rpm packaging. 2013-07-08 18:05:38 -05:00