[
https://issues.apache.org/jira/browse/NIFI-7719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17221469#comment-17221469
]
ASF subversion and git services commented on NIFI-7719:
-------------------------------------------------------
Commit 3612973a47d7b9134a8852e0a26f3f92c8a99529 in nifi's branch
refs/heads/main from Bryan Bende
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=3612973 ]
NIFI-7929 Resolving conflicts after rebasing on top of NIFI-7719
This clsoes #4610.
Signed-off-by: Bryan Bende <[email protected]>
> 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
> Fix For: 1.13.0
>
> Time Spent: 20m
> 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)
