pvillard31 commented on PR #8630:
URL: https://github.com/apache/nifi/pull/8630#issuecomment-2050213770
Thanks @exceptionfactory! What about the following approach where I have the
DefaultAuthorizer moved to its own class and in authorizers.xml, have something
like:
````
<authorizer>
<identifier>default-authorizer</identifier>
<class>org.apache.nifi.registry.security.authorization.DefaultAuthorizer</class>
<property name="Read Only">false</property>
</authorizer>
````
And then instead of
````
public Authorizer getAuthorizer() throws AuthorizerFactoryException {
if (authorizer == null) {
if (properties.getSslPort() == null) {
// use a default authorizer... only allowable when running
not securely
authorizer = createDefaultAuthorizer();
} else {
````
I would instantiate the DefaultAuthorizer the same way as the other ones are
instantiated.
Thoughts?
If we think this is not worth it because it is for a very specific use case,
I'll maintain my own version of the NiFi Registry.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
