ramackri commented on PR #1135: URL: https://github.com/apache/ranger/pull/1135#issuecomment-5194781216
## SPIFFE outbound auth — aligned with RANGER-5700 (#1096) Addressing review feedback: SPIFFE-based authn via HTTP headers does **not** need per-plugin install templates. ### What changed (commits `ab1b32df8`, `a225c83d4`) - **Removed** all plugin `install.properties`, `*-audit-changes.cfg`, and `*-security-changes.cfg` SPIFFE entries (51 files) — zero net diff vs `master` for plugin templates. - **Outbound auth** is handled in Java only (`RangerAuditServerDestination` + `PluginHeaderAuthConfig` + `SpiffeIdentityResolver` + `RangerRESTClient.setTrustedAuthHeaders()`), using the audit destination prefix (JWT-style), not `ranger.<service>.authn.*` security props. This mirrors [#1096](https://github.com/apache/ranger/commit/22fbc813d576b2d386f7baaf51a1895c96b1bece): configure auth on the component that owns the HTTP flow, not in every plugin security config. ### How operators enable outbound SPIFFE Add one property to `ranger-<service>-audit.xml`: ```xml <property> <name>xasecure.audit.destination.auditserver.authn.header.enabled</name> <value>true</value> </property> ``` On SPIRE-managed workloads, the SPIFFE ID is resolved automatically from the default identity file (`/var/run/secrets/spiffe.io/identity/spiffe`) or `SPIFFE_ID` env; header name defaults to `X-Spiffe-Id`. Optional overrides: `authn.header.spiffe`, `authn.spiffe.file`, `authn.spiffe.value` under the same audit destination prefix. ### Follow-on Inbound SPIFFE validation on the audit ingestor remains in PR4 (RANGER-5722), analogous to PDP/Admin inbound SPIFFE in #1096. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
