Description
It looks like we have a very "generic" code in SentryGenericPolicyProcessor that creates DelegateSentryStore based on the class name which may be changed in configuration. This is very cute, but sounds quite complicated to me. I don't know the history here, but I would suggest removing this and just creating DelegateSentryStore directly.
Attachments
Attachments
Issue Links
- is related to
-
SENTRY-404 Extending Sentry thrift interface and adding a processor for generic authorization model
- Resolved
- links to