Package io.confluent.security.auth.s2s
package io.confluent.security.auth.s2s
-
ClassDescriptionIn-memory snapshot of the two-category Cedar policy bundle,
{"L2": {policyId -> cedar}, "L3": {policyId -> cedar}}, loaded from the broker config keyConfluentConfigs.S2S_AUTHZ_POLICIES.Input passed toS2SDecisionSource.evaluate(EvaluationInput).Per-layer S2S AuthZ decision metric:s2s-authz-checks-rate, taggedlayer(L2/L3b),outcome(allow/deny/continue/abstain), andtokenType.L2 connection-level S2S AuthZ GATE: evaluates the calling service's SPIRE-mTLS cert SPIFFE-ID against theL2Cedar policy category and emits aS2SDenyRuleon a veto.SRJ Cedar integration point for the L2 connection-level AuthZ provider.Pluggable decision source for the S2S AuthZ provider.Outcome ofS2SDecisionSource.evaluate(EvaluationInput), widened beyond the tri-stateS2SDecisionSource.Decisionwith the diagnostic detail the observability layer needs: anoutcomelabel (one ofallow/deny/continue/abstain, layer-specific — seeS2SConnectionLevelDecisionSource/S2SServiceLevelDecisionSource), and the SRJDecision's determining policy IDs (reasons) andpassName, when the underlying SRJ authorizer actually ran (both are empty when no authorizer is installed, i.e.DENY-only rule carrying the SPIFFE-ID that triggered the denial.ALLOW-only rule carrying the system-LATsubSPIFFE-ID that earned the grant.L3b — the service-level AuthZ VERDICT, dispatched byEmbeddedAuthorizeras the sole verdict for any request whose principal carries a system LAT (tokenType == SYSTEM_LOGICAL_ACCESS_TOKEN), in place of the traditional RBAC/ACL chain.SRJ Cedar integration point for the L3b service-level AuthZ provider.