GitHub user kevdoran opened a pull request:

    https://github.com/apache/nifi-registry/pull/30

     NIFIREG-46 Add authorizedActions field to Bucket

    This builds upon PR #29 (NIFIREG-33), so only the commits on top of that 
need to considered.
    
    The API now returns an additional field for a Bucket, telling the client 
what actions they are authorized to perform on that bucket. For example:
    
    ```
    "authorizedActions": ["read", "write", "delete"]
    ```
    
    With this change, `/buckets` is now a convenient initial endpoint to use to 
both check authentication of the client identity and discover buckets and 
authorizations available to the client.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kevdoran/nifi-registry NIFIREG-46

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi-registry/pull/30.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #30
    
----
commit c0048e5c5ee975470df69012be32b3dac88f023f
Author: Kevin Doran <[email protected]>
Date:   2017-10-12T17:54:34Z

    NIFIREG-33 Add LDAP and JWT auth support
    
    - Adds LdapIdentityProvider for authentication
    - Adds /access/token endpoint for generating JWT for users that can 
authenticate with a configured IdenitiyProvider
    - Adds JwtAuthenticationProvider for authentication
    - Adds KeyService for key generation and tracking for signing JWTs
    - Adds LdapUserGroupProvider for authorization
    - Adds LDAP integration tests
    - Refactors nifi-registry-security-api-impl into nifi-registry-framework
    - Refactors all security related packages, such as o.a.n.r.authorization 
and o.a.n.r.authentication, under org.apache.nifi.registry.security

commit f70f02a79d62701eb57bb9504f7ed1851fe3d04e
Author: Kevin Doran <[email protected]>
Date:   2017-11-01T19:02:19Z

    NIFIREG-46 Add authorizedActions field to Bucket

----


---

Reply via email to