Provides a mechanism for creating a KerberosUser from a principal and ticket cache that other components are able to use in order to perform authentication using Kerberos. By encapsulating this information into a Controller Service and allowing other components to make use of it an administrator is able to choose which users are allowed to use which ticket caches and principals. This provides a more robust security model for multi-tenant use cases.


Kerberos, Ticket, Cache, Principal, Credentials, Authentication, Security


In the list below, the names of required properties appear in bold. Any other properties (not in bold) are considered optional. The table also indicates any default values, and whether a property supports the NiFi Expression Language.

Display NameAPI NameDefault ValueAllowable ValuesDescription
Kerberos PrincipalKerberos PrincipalKerberos principal to authenticate as. Requires nifi.kerberos.krb5.file to be set in your
Supports Expression Language: true (will be evaluated using variable registry only)
Kerberos Ticket Cache FileKerberos Ticket Cache FileKerberos ticket cache associated with the principal.

This property requires exactly one file to be provided..

Supports Expression Language: true (will be evaluated using variable registry only)

State management:

This component does not store state.


Required PermissionExplanation
access ticket cacheAllows user to define a ticket cache and principal that can then be used by other components.

System Resource Considerations:

None specified.