Per‑User Impersonation / Delegated Execution for Actions
A
Andrei Sergio Rodriguez Barriga
We need Port to support executing self‑service actions as the real user, not as a shared technical account. Today, actions that call tools like GitHub or Jira are executed with an app token, so in those tools every change appears as coming from a generic user. This breaks per‑user traceability required by an external zero‑trust banking audit, is considered a high security risk, and blocks us from safely scaling self‑service to 1,500+ engineers and multiple companies in our group.
Requested capability:
* OAuth2‑based delegated authorization so each Port user can link their own GitHub/Jira account and actions run with their token.
* A consistent “execute as user” model across integrations (GitHub first, then Jira, others later).
* Configurable backend for actions: keep current “machine token” mode, and add a new user‑session/OAuth mode that respects Port RBAC and IdP policies.
This is a blocker for audit compliance, enterprise‑wide adoption, and for comparing Port fairly with other IDPs that already support per‑user execution.
S
Shilton JoJo
We are trying to use an LLM chat bot to connect with the Port MCP service and execute actions as the user who initiated it.
This is currently not possible since the bot cannot assume the user's identity using oauth.