[
https://issues.apache.org/jira/browse/NIFI-7719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17221391#comment-17221391
]
ASF subversion and git services commented on NIFI-7719:
-------------------------------------------------------
Commit 6e9bef14287267b5d28129c0fb68fbc7a3e218d8 in nifi's branch
refs/heads/main from Bryan Bende
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=6e9bef1 ]
NIFI-7719 Initial refactoring to NiFiClient in CLI to support additional
authentication mechanisms
Added command options for basic auth and bearer token and updated
NiFiClientFactory to create the appropriate RequestConfig
Added get-token command for NiFi
Update NiFi Registry CLI commands based on nifi-registry-client 0.8.0-SNAPSHOT
Implementing commands for NiFi and NiFi Registry to obtain a token via SPNEGO
and to logout a given token
Add Keberos JAAS classes for using the ticket cache, update
GetAccessTokenSpnego methods to fallback to ticket cache when no keytab or
password is specified
Use released 0.8.0 version of registry client
Signed-off-by: Pierre Villard <[email protected]>
This closes #4461.
> 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)
