[
https://issues.apache.org/jira/browse/NIFIREG-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16225007#comment-16225007
]
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_r147711295
--- Diff:
nifi-registry-framework/src/main/resources/db/migration/V1__Initial.sql ---
@@ -43,4 +43,11 @@ CREATE TABLE FLOW_SNAPSHOT (
COMMENTS VARCHAR(4096),
PRIMARY KEY (FLOW_ID, VERSION),
FOREIGN KEY (FLOW_ID) REFERENCES FLOW(ID)
+);
+
+CREATE TABLE SIGNING_KEY (
+ ID VARCHAR2(50) NOT NULL,
+ TENANT_IDENTITY VARCHAR2(50) NOT NULL UNIQUE,
+ KEY_VALUE VARCHAR2(50) NOT NULL,
+ PRIMARY KEY (ID)
--- End diff --
Let me know if the preference is to make this V2__*.sql. I added it here
assuming that we didn't have to worry about any production deployments of
nifi-registiry-0.0.1-SNAPSHOT 😄
> 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)
