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

Posted to issues@nifi.apache.org by "Bryan Bende (Jira)" <ji...@apache.org> on 2020/08/10 13:23:00 UTC

[jira] [Updated] (NIFI-7719) Allow NiFi CLI to use additional authN mechanisms

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

Bryan Bende updated NIFI-7719:
------------------------------
    Status: Patch Available  (was: In Progress)

> Allow NiFi CLI to use additional authN mechanisms 
> --------------------------------------------------
>
>                 Key: NIFI-7719
>                 URL: https://issues.apache.org/jira/browse/NIFI-7719
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Bryan Bende
>            Assignee: Bryan Bende
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently the CLI supports only 2-Way TLS with an optional proxied entity.
> It would be helpful to support the other mechanisms that NiFi and NiFi Registry currently supports, mainly obtaining a token from the /token end-points, and obtaining a token using SPNEGO against the /token/kerberos endpoints.



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