You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Kevin Doran (Jira)" <ji...@apache.org> on 2020/09/03 18:21:00 UTC

[jira] [Resolved] (NIFIREG-411) Add additional authenitcation methods to nifi registry client

     [ https://issues.apache.org/jira/browse/NIFIREG-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Doran resolved NIFIREG-411.
---------------------------------
    Fix Version/s: 0.8.0
       Resolution: Fixed

> Add additional authenitcation methods to nifi registry client
> -------------------------------------------------------------
>
>                 Key: NIFIREG-411
>                 URL: https://issues.apache.org/jira/browse/NIFIREG-411
>             Project: NiFi Registry
>          Issue Type: Improvement
>    Affects Versions: 0.7.0
>            Reporter: Bryan Bende
>            Assignee: Bryan Bende
>            Priority: Major
>             Fix For: 0.8.0
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Currently nifi-registry-client only allows client certs with an optional proxied entity. We should add the ability to obtain an access token by providing login credentials and be able to pass that token back on future requests.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)