JWT Audience and Issuer Claim Validation

Impala validates the iss (Issuer) and aud (Audience) claims in JWT tokens to prevent token redirection attacks.

Overview

Cloudera Runtime 7.3.3 supports validation of JWT token claims to enhance security in federated authentication scenarios. When configured, Impala enforces iss (issuer) and aud (audience) claim validation, ensuring that tokens are issued by trusted authorities and intended specifically for Impala. This prevents token redirection attacks where a valid token intended for one service is misused against another.

Configuration through --oauth_servers

Claim validation is configured within the --oauth_servers JSON schema. Each OAuth provider entry can specify issuer and audience restrictions as JSON arrays:

Table 1. JWT claim validation configuration
Configuration Field Type Description
issuerClaims STRING JSON array of trusted issuer strings. If set, the iss claim in incoming tokens must match one of these values exactly. Tokens with missing or mismatched iss claims are rejected with a 401 Unauthorized response. Such as: ["https://idp1.example.com", "https://idp2.example.com"]
audienceClaims STRING JSON array of valid audience strings. If set, the aud claim in incoming tokens must match one of these values. If the aud claim is an array (as per JWT specification), validation passes if at least one value matches the configured list. Tokens with missing or mismatched aud claims are rejected. Example: ["impala", "impala-prod"]

Validation behavior

Fail-closed validation
Any token failing claim validation results in immediate authentication failure (401 Unauthorized). No partial or degraded access is granted.
Audit logging
Failed claim validations are logged at INFO or WARN level, specifying which claim failed without logging sensitive token data. This assists in troubleshooting authentication issues.
Backward compatibility
If issuerClaims and audienceClaims are not configured within an --oauth_servers entry, claim validation is skipped and existing JWT configurations continue to work without modification.

Examples

Validate issuer and audience claims in --oauth_servers:

--oauth_servers='[{
  "issuer": "https://auth.example.com",
  "issuerClaims": ["https://auth.example.com"],
  "audienceClaims": ["impala", "impala-service"],
  "jwks_uri": "https://auth.example.com/.well-known/jwks.json"
}]'

Multiple OAuth providers with different claim requirements:

--oauth_servers='[
  {
    "issuer": "https://idp1.example.com",
    "issuerClaims": ["https://idp1.example.com"],
    "audienceClaims": ["impala-prod"],
    "jwks_uri": "https://idp1.example.com/.well-known/jwks.json"
  },
  {
    "issuer": "https://idp2.example.com",
    "issuerClaims": ["https://idp2.example.com"],
    "audienceClaims": ["impala", "shared-service"],
    "jwks_uri": "https://idp2.example.com/.well-known/jwks.json"
  }
]'