GitHub user RB-ETArch created a discussion: Is STS Token Passthrough Supported in Polaris Federated Catalogs?
I am evaluating catalog federation behavior in a data lakehouse setup using Apache Iceberg with Apache Polaris. **Architecture:** - One central enterprise catalog - Multiple BU level child catalogs federated into the central catalog **Expected flow (based on my understanding):** - Client queries an Iceberg table through the central catalog - Central catalog forwards the request to the appropriate BU catalog after RBAC validation - BU catalog returns table metadata and an STS token - Central catalog returns the BU catalog’s metadata and the same STS token back to the client **Actual behavior observed:** - BU catalog does return metadata + STS token - Central catalog drops/ignores the BU-provided STS token - Central catalog generates a new STS token and sends that to the client instead **Question:** Is this the expected behavior for Polaris catalog federation (i.e., central catalog always re-issues STS tokens), or is this a bug / misconfiguration? GitHub link: https://github.com/apache/polaris/discussions/4929 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
