agent-substrate / agent-substrate/substrate

How should an in-cluster user-owned gateway identify an actor?

Abierto
#1,228 1 comentario 0 reacciones 1 asignado Reclamado por @haiyanmeng Ver en GitHub
area/identity area/network kind/feature
Lenguaje dominante
Go
Estrellas
1.8k
Forks
316
Merge medio
2 d 43 min
PR fusionados (30 d)
287

Descripción

**Question:**
For egress traffic from an actor to an in-cluster user-owned gateway (not Substrate's egress gateway), how should the user-owned gateway identify the actor?

**Option 1:**
@haiyanmeng did a raw exploration in #1219 by modifying the Substrate egress gateway to forward the actor identity to cluster-local origins, without realizing that token exchange is included in the [egress policy](https://docs.google.com/document/d/1s2klDhbF2mB5sslwUyZBdyXD7JqRt8FWONwJ7wgsomE/edit?tab=t.0) now.

**Option 2:**
@keithmattix and @EItanya pointed out that the token exchange feature proposed in the [egress policy](https://docs.google.com/document/d/1s2klDhbF2mB5sslwUyZBdyXD7JqRt8FWONwJ7wgsomE/edit?tab=t.0) can be a good fit for this use case.

cc @keithmattix @EItanya @LiorLieberman @bowei

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.