StandaloneKerberosKeytabUserService 2.11.0.4.13.0.0-948

Bundle
com.cloudera | nifi-cdf-standalone-kerberos-user-service-nar
Description
Provides a KerberosUser backed by a ticket cache maintained by a standalone JVM. Use this service when acquiring or refreshing Kerberos tickets requires krb5.conf settings, such as [libdefaults], that are incompatible with the NiFi JVM's global Kerberos configuration. See Additional Details for global krb5.conf requirements.
Tags
Authentication, Cache, Credentials, Kerberos, Keytab, Principal, Security, Ticket
Input Requirement
Supports Sensitive Dynamic Properties
false
  • Additional Details for StandaloneKerberosKeytabUserService 2.11.0.4.13.0.0-948

    StandaloneKerberosKeytabUserService

    Kerberos Configuration

    This service starts a standalone JVM to authenticate with the configured Kerberos Principal and Kerberos Keytab. The standalone JVM uses the configured Kerberos Configuration File to locate the KDC, acquire a ticket-granting ticket, and maintain a ticket cache for the main NiFi JVM.

    This service is intended for cases where acquiring or refreshing the initial ticket requires Kerberos configuration settings, especially [libdefaults], that cannot be used safely as the NiFi JVM’s global Kerberos configuration.

    The service sends startup configuration to the standalone JVM through stdin JSON. This avoids exposing credentials through process command arguments.

    The standalone JVM configuration is not used for all Kerberos operations. When NiFi components use the ticket cache to connect to a kerberized service, the service ticket request still happens in the main NiFi JVM. The main NiFi JVM uses its own krb5.conf to determine the target service realm and locate the KDC for that realm.

    For this reason, the main NiFi krb5.conf must include enough information to locate the additional realm used by this service. It does not need the service principal or keytab, but it does need the realm definition and host-to-realm mappings for the target services.

    For example, if this service authenticates as admin@EXAMPLE.COM and NiFi connects to services in EXAMPLE.COM, the main NiFi krb5.conf should include entries similar to the following:

    [realms]
      EXAMPLE.COM = {
        kdc = kdc.example.com:88
      }
    
    [domain_realm]
      postgres.example.com = EXAMPLE.COM
      .example.com = EXAMPLE.COM
    

    The exact host names should match the hosts used by the client component or driver. For example, if a JDBC connection uses localhost, then localhost must map to the correct realm when that is the expected service host.

    Troubleshooting

    Errors such as No service creds can indicate that the standalone JVM successfully acquired the initial ticket, but the main NiFi JVM could not acquire a service ticket for the target service. Check that the main NiFi krb5.conf includes the target realm in the [realms] section and maps the target service host to that realm in the [domain_realm] section.

Properties