Integration / Apache NiFi Interview Questions
How does NiFi handle security — TLS, authentication, and authorization?
NiFi provides a comprehensive security model covering transport encryption, user authentication, and fine-grained authorization.
TLS / Transport Encryption: NiFi can be configured to serve its UI and API exclusively over HTTPS. TLS is configured in nifi.properties using a keystore (server certificate) and truststore (CA certificates for client certificate validation). The tls-toolkit utility generates self-signed certificates and keystores for development clusters.
Authentication — NiFi supports multiple Login Identity Providers:
Client Certificate: Mutual TLS — the browser or API client presents a certificate. The Common Name (CN) becomes the NiFi identity.
LDAP / Active Directory: Username and password validated via LdapIdentityProvider.
Kerberos: Single sign-on via Kerberos ticket; the authenticated principal becomes the NiFi identity.
OIDC / OAuth2: Integration with Keycloak, Okta, or Azure AD via OpenID Connect.
Authorization: NiFi uses a policy-based model. Every resource (processor, connection, Process Group, provenance) has access policies — Read, Write, and Operate — that users or groups can be granted or denied. The authorizers.xml file configures the authorization provider. LDAP-based groups can be imported for group-level policy management.
More Related questions...