Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Design and implement a mechanism for refreshing client ACLs #10

Open
narinearraul opened this issue Jan 29, 2017 · 0 comments
Open

Design and implement a mechanism for refreshing client ACLs #10

narinearraul opened this issue Jan 29, 2017 · 0 comments

Comments

@narinearraul
Copy link
Member

mkistler commented on Mar 16, 2016
Clients must issue advance for every ACL they have read access to, but this set of ACLs can change, and we currently have no mechanism for refreshing or updating the client with the correct set of ACLs. We need to design and implement this mechanism.

mkistler commented on Mar 18, 2016
We actually need to address two related issues:

  1. Client must refresh it's set of readable ACLs when necessary
  2. Queue bindings must be updated when ACLs change

Client must clean up DB to eliminate any data not for ACLs the client can read.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant