agent-substrate / agent-substrate/substrate

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

未关闭
#1,228 1 条评论 0 个 reaction 已指派 1 人 已被 @haiyanmeng 认领 在 GitHub 查看
area/identity area/network kind/feature
主要语言
Go
星标
1.8k
派生
316
平均合并
2 天 43 分钟
30 天内合并 PR
287

描述

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

贡献指南

打开贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。