[
https://issues.apache.org/jira/browse/NIFIREG-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16669128#comment-16669128
]
Bryan Bende commented on NIFIREG-206:
-------------------------------------
Wanted to leave a note that I started this work here:
[https://github.com/bbende/nifi-registry/commit/110bd20bcb12370449b1062f828ec5560bc0acd7]
It allows anonymous access to a secure instance, and if you create a user with
identity of "anonymous" they can only see the buckets granted to that user.
The issue is that the front-end currently relies on getting a 401 for a
non-authenticated user to determine when to display the login page, so with
this change there is no way to get to the login page.
So we'll need to figure out the correct changes to make to the front-end.
> Support anonymous read-only access to a bucket
> ----------------------------------------------
>
> Key: NIFIREG-206
> URL: https://issues.apache.org/jira/browse/NIFIREG-206
> Project: NiFi Registry
> Issue Type: Improvement
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Minor
>
> Currently in a secure NiFi Registry, all users must authenticate with a valid
> identity based on one of the authentication mechanisms that has been
> configured (client certs, LDAP, or kerberos). If a request comes in with no
> user credentials, then we create an anonymous user which will be denied
> access.
> We should support a way to indicate that a bucket can be read by anyone (i.e.
> the anonymous user). This would allow there to be a bucket where publicly
> available flows can be shared, but only those users with write permissions to
> the bucket can add flows, and other buckets can remain private.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
