This message was deleted.
# general
s
This message was deleted.
f
We have abstractions for access control, but currently there is no basic implementation out of the box in OSS. @Zac Policzer, can you advise on whether users should focus their attention on the DynamicAccessController or the AuthorizerService? Are we phasing out one of them?
z
DynamicAccessController is the older one that currently does ACL enforcement, but it doesn't do much management. AuthorizerService is the newer one that provides the simplified interface for management in the Venice Controller
It's a bit of tech debt to get rid of the former, and one that we haven't I guess had a lot of initiative on with fast client coming along and "potentially" deprecating the router.
Hrm. Though on second glance, it looks like we're still using this one in the server acl enforcement as well. So maybe the answer is to just remove from this interface the management side of things and just let it keep enforcing.
f
Can they / should they be merged into one?
What would be the use case for implementing one but not the other?
z
Only reason I can think of is if you wanted the object/implementation to be lighter in the read path vs. the control plane. But yeah, my cursory glance through makes me think we can just swap one for the other. The newer one appears to be a superset of the api's of the older one.
f
We should do that… and we can mark in the JavaDoc which of the functions are used in the hot path versus not
c
Thanks for the info!
Much appreciated