Support for Multiple Token Identity Providers
Impala introduces unified configuration for multiple identity providers (IDPs), enabling federated authentication scenarios where tokens may come from different trusted sources.
Overview
Cloudera Runtime 7.3.3 introduces support for configuring and trusting multiple identity providers (IDPs) for JWT and OAuth token authentication. This feature enables federated authentication in enterprise environments where authentication tokens may be issued by different trusted sources.
The unified IDP configuration framework improves flexibility for multi-cloud, multi-tenant, and hybrid deployments where different services may use different authentication providers.
Previous legacy auth approach (deprecated)
Earlier versions of Impala used individual configuration flags to support a single provider config per legacy auth setup. Legacy mode was based on single JWKS and claim settings configured through jwt_ and oauth_ legacy flags:
- --jwt_token_auth
- --jwks_url
- --jwt_custom_claim_username
- OAuth legacy equivalents:
- --oauth_token_auth
- --oauth_jwks_url
- --oauth_jwks_file_path
- --oauth_jwks_ca_certificate
- --oauth_jwks_verify_server_certificate
- --oauth_jwks_pulling_timeout_s
- --oauth_jwks_update_frequency_s
- --oauth_jwt_custom_claim_username
- --oauth_jwt_validate_signature
- --oauth_allow_without_tls
The unified configuration path for current deployments is --oauth_servers, which supports multiple OAuth providers in a single JSON configuration.
Benefits for federated authentication
The multi-IDP feature enables several important use cases:
- Enterprise federation- Support authentication from corporate identity management systems (e.g., Active Directory, Okta, Azure AD) simultaneously in a single Impala cluster
- Organizational mergers- Continue accepting tokens from pre-merger identity systems during transition periods
- Multi-cloud deployments: Accept tokens issued by cloud-provider identity services (AWS IAM, GCP Cloud Identity, Azure AD) in on-premises Impala instances
- Third-party integrations- Allow partner or customer systems with their own identity providers to authenticate with shared Impala services
- Hybrid architectures- Support seamless authentication across on-premises and cloud deployments using their respective identity providers
