[
https://issues.apache.org/jira/browse/NIFI-14686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Turcsanyi updated NIFI-14686:
-----------------------------------
Description:
Kerberos User Service and Kerberos Service Name properties are always shown in
Kafka3ConnectionService but they are only relevant if GSSAPI SASL Mechanism is
used.
Similar to Username / Password, the Kerberos properties should be displayed
only for the right SASL Mechanism. They can also be mandatory because GSSAPI
does not work otherwise.
SSL Context Service is only applied to SSL/SASL_SSL Security Protocols so it
can be made dependent of those values.
Plus code refactor: KerberosDelegatingLoginConfigProvider was used as a
sub-delegator in DelegatingLoginConfigProvider and routed different Kerberos
configurations (KerberosCredentialsService, KerberosUserService, direct
properties). In NiFI 2.x only KerberosUserService is available, so the
delegator class is not needed anymore.
was:
Kerberos User Service and Kerberos Service Name properties are always shown in
Kafka3ConnectionService but they are only relevant if GSSAPI SASL Mechanism is
used.
Similar to Username / Password, the Kerberos properties should be displayed
only for the right SASL Mechanism. They can also be mandatory because GSSAPI
does not work otherwise.
SSL Context Service is only applied to SSL/SASL_SSL Security Protocols so it
can be made dependent of those values.
Plus code refactor: KerberosDelegatingLoginConfigProvider was used as a
sub-delagator in DelegatingLoginConfigProvider and routed different Kerberos
configurations (KerberosCredentialsService, KerberosUserService, direct
properties). In NiFI 2.x only KerberosUserService is available, so the
delegator class is not needed anymore.
> Add dependsOn for Kerberos and SSL properties in Kafka3ConnectionService
> ------------------------------------------------------------------------
>
> Key: NIFI-14686
> URL: https://issues.apache.org/jira/browse/NIFI-14686
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Peter Turcsanyi
> Assignee: Peter Turcsanyi
> Priority: Minor
>
> Kerberos User Service and Kerberos Service Name properties are always shown
> in Kafka3ConnectionService but they are only relevant if GSSAPI SASL
> Mechanism is used.
> Similar to Username / Password, the Kerberos properties should be displayed
> only for the right SASL Mechanism. They can also be mandatory because GSSAPI
> does not work otherwise.
> SSL Context Service is only applied to SSL/SASL_SSL Security Protocols so it
> can be made dependent of those values.
> Plus code refactor: KerberosDelegatingLoginConfigProvider was used as a
> sub-delegator in DelegatingLoginConfigProvider and routed different Kerberos
> configurations (KerberosCredentialsService, KerberosUserService, direct
> properties). In NiFI 2.x only KerberosUserService is available, so the
> delegator class is not needed anymore.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
