[
https://issues.apache.org/jira/browse/NIFIREG-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16242066#comment-16242066
]
ASF GitHub Bot commented on NIFIREG-33:
---------------------------------------
Github user kevdoran commented on a diff in the pull request:
https://github.com/apache/nifi-registry/pull/29#discussion_r149377495
--- Diff:
nifi-registry-properties/src/main/java/org/apache/nifi/registry/properties/NiFiRegistryProperties.java
---
@@ -49,6 +49,8 @@
public static final String SECURITY_NEED_CLIENT_AUTH =
"nifi.registry.security.needClientAuth";
public static final String SECURITY_AUTHORIZERS_CONFIGURATION_FILE =
"nifi.registry.security.authorizers.configuration.file";
public static final String SECURITY_AUTHORIZER =
"nifi.registry.security.authorizer";
+ public static final String
SECURITY_IDENTITY_PROVIDER_CONFIGURATION_FILE =
"nifi.registry.security.identity.provider.configuration.file";
--- End diff --
Yep, good catch. Will update this.
> Add LDAP and JWT identity providers NiFi Registry security framework
> --------------------------------------------------------------------
>
> Key: NIFIREG-33
> URL: https://issues.apache.org/jira/browse/NIFIREG-33
> Project: NiFi Registry
> Issue Type: Improvement
> Reporter: Kevin Doran
> Assignee: Kevin Doran
>
> The initial addition of a security model to the NiFi Registry framework only
> included support for certificates as a means of establishing client identity
> for authentication.
> In order to support more flexible methods of client authentication, this
> ticket is to provider two new identity providers:
> * LDAPProvider - will verify username/password for authentication and allow
> JWT token generation via the REST API
> * JWTIdentityProvider - will authenticate tokens that were generated by the
> registry on subsequent requests.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
