Github user alopresto commented on the pull request:
https://github.com/apache/nifi/pull/452#issuecomment-220464739
@mcgilman thanks for the response above. It feels a little to me like the
authorizer has gotten conflated with user and group management tasks. If the
authorizer' responsibility is strictly to manage and enforce policy, then we
probably want a `UserService` to manage user retrieval, modification, etc.
Maybe this is injected into the authorizer to allow various identity provider
implementations (LDAP, Kerberos, etc.) to work with various authorizers
(Ranger, NiFi internal, etc.) I'm not going to hold up this step with the
understanding there are still more design decisions to be made.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
