agent-substrate / agent-substrate/substrate

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

Ouverte
#1,228 1 commentaire 0 réactions 1 personne assignée Réclamée par @haiyanmeng Voir sur GitHub
area/identity area/network kind/feature
Langage dominant
Go
Étoiles
1.8k
Forks
316
Merge moyen
2 j 43 min
PR mergées (30 j)
287

Description

**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

Guide de contribution

Ouvrir le guide de contribution

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.