Skip to content
This repository has been archived by the owner on Jan 7, 2020. It is now read-only.

Add tests for app revocation scenarios #331

Open
bochaco opened this issue Dec 17, 2018 · 0 comments
Open

Add tests for app revocation scenarios #331

bochaco opened this issue Dec 17, 2018 · 0 comments
Milestone

Comments

@bochaco
Copy link
Contributor

bochaco commented Dec 17, 2018

When an application is revoked, any default container that app was having accessed to is reencrypted. We should have tests which verify the expected behaviour for when this happens, specially when more than one application has granted access to the same set of default containers, e.g. if one app is revoked a second app should be able to read the content of the default container with the new encryption keys.

@bochaco bochaco added this to the next milestone Dec 17, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant