[
https://issues.apache.org/jira/browse/RANGER-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18133316#comment-18133316
]
Abhishek Kumar commented on RANGER-5700:
----------------------------------------
Merged in ranger-2.10:
https://github.com/apache/ranger/commit/dbb54f55b137c837f35c393940a498c2fd82aed6
> Support SPIFFE-based authn via HTTP Headers
> --------------------------------------------
>
> Key: RANGER-5700
> URL: https://issues.apache.org/jira/browse/RANGER-5700
> Project: Ranger
> Issue Type: Improvement
> Components: pdp, Ranger
> Reporter: Abhishek Kumar
> Assignee: Abhishek Kumar
> Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Header based authentication was added in RANGER-5499.
> Extend it to add support for SPIFFE-based authentication using HTTP headers,
> enabling service-to-service authentication for workload service accounts in
> Kubernetes-based trusted environments.
> SPIFFE: [https://spiffe.io/docs/latest/spiffe-about/overview/]
> In Kubernetes deployments with a service mesh (e.g., Istio), the sidecar
> proxy establishes and verifies workload identity via mutual TLS and
> represents it as a SPIFFE ID
> ({{{}spiffe://<trust-domain>/ns/<namespace>/sa/<service-account>{}}}).
> Because the mesh has already attested and verified this identity, the
> receiving service only needs to read and trust the SPIFFE ID forwarded to it
> as an HTTP header.
> The Jira tracks support in following servers: ranger-admin, ranger-pdp
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
