[
https://issues.apache.org/jira/browse/NIFIREG-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16193182#comment-16193182
]
ASF GitHub Bot commented on NIFIREG-9:
--------------------------------------
Github user kevdoran commented on the issue:
https://github.com/apache/nifi-registry/pull/14
@bbende I restructured the modules based on your suggestion. I now have the
following modules:
```
nifi-registry-security // just a container module, packaged
as pom
+--nifi-registry-security-api // gets placed in lib dir for others
to implement against
+--nifi-registry-security-api-impl // NiFi Registry's implementation of
security-api
+--nifi-registry-security-framework // extends registry-framework to add
security
```
Let me know if you agree with this or if it is overkill for what we need.
Technically `nifi-registry-security-api-impl` and
`nifi-registry-security-framework` can be combined (technically, they could
even be part of `nifi-registry-framework`). I can consolidate some of these if
you'd rather keep a flatter, more condensed module structure. Let me know.
> Define web REST API endpoints for user, group, and policy management
> --------------------------------------------------------------------
>
> Key: NIFIREG-9
> URL: https://issues.apache.org/jira/browse/NIFIREG-9
> Project: NiFi Registry
> Issue Type: New Feature
> Reporter: Kevin Doran
> Assignee: Kevin Doran
> Fix For: 0.0.1
>
>
> NIFIREG-8 defined web REST API endpoints for domain objects such as buckets
> and flows.
> This ticket scopes work to build on that by adding endpoints for additional
> resources to facilitate user, group, and policy management.
> The interface for user, group, and policy management will be based on the
> NiFi API so as to minimize the effort for NiFi API clients to be reused for
> NiFi Registry.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
