# Feature request: Browser/device-flow admin login for OpenAI CLI and Terraform/Pulumi

**URL:** <https://community.openai.com/t/feature-request-browser-device-flow-admin-login-for-openai-cli-and-terraform-pulumi/1395669>\
**Category:** API\
**Tags:** api, oauth\
**Created:** [September 8, 2026, 4:14am UTC](https://community.openai.com/t/feature-request-browser-device-flow-admin-login-for-openai-cli-and-terraform-pulumi/1395669 "2026-09-08T04:14:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![vicaya](https://avatars.discourse-cdn.com/v4/letter/v/a3d4f5/32.png) [@vicaya](https://community.openai.com/u/vicaya)\
**Post date:** [September 8, 2026, 4:14am UTC](https://community.openai.com/t/feature-request-browser-device-flow-admin-login-for-openai-cli-and-terraform-pulumi/1395669/1 "2026-09-08T04:14:05Z")

</div>

Please support interactive OAuth authentication for the OpenAI Administration API, analogous to `aws sso login`.

My use case is running Terraform/Pulumi as a human administrator to provision projects, service accounts, and workload identity federation issuer/mapping configuration without creating a persistent Admin API key.

Desired workflow (proposed commands):

```auto
openai login --org <organization>
# Browser authentication; device authorization available for remote terminals

terraform apply
# Or: pulumi up

```

Requested capabilities:

- Short-lived Admin API access tokens scoped to the authenticated user’s organization permissions.

- Browser authorization with PKCE and a device authorization option.

- A documented credential helper/cache consumed by the CLI, SDKs, and IaC providers, with automatic refresh.

- Organization/profile selection, logout/revocation, and enforcement of SSO/MFA and session policies.

- API and IaC support for provisioning WIF issuers and service-account mappings using that human admin session.

The immediate goal is keyless human bootstrap of workload federation. Separately, narrowly scoped federated Admin API access would enable subsequent CI-driven infrastructure management without storing an Admin API key.

Is this planned, or is there an existing supported workflow or public issue to follow?

P.S. Anthropic already supports this as expected.

---

<div class="post-metadata">

**Author:** ![OpenAI\_Support](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/openai_support/32/561845_2.png) [@OpenAI\_Support](https://community.openai.com/u/OpenAI_Support)\
**Post date:** [October 26, 2026, 11:13pm UTC](https://community.openai.com/t/feature-request-browser-device-flow-admin-login-for-openai-cli-and-terraform-pulumi/1395669/2 "2026-10-26T23:13:58Z")

</div>

Appreciate you sharing this, @vicaya!

I can see why you’d want to manage resources through CLI without creating or storing an Admin API key.

You can use the [OpenAI CLI](https://developers.openai.com/api/docs/libraries/openai-cli) and [Terraform provider](https://developers.openai.com/api/docs/guides/terraform) to create projects and service accounts with an Admin API key. [Workload identity federation](https://developers.openai.com/api/docs/guides/workload-identity-federation) provides short-lived workload credentials, but those tokens can’t currently call Admin API endpoints. These docs may help with parts of your workflow.

That said, I’ll pass your request for keyless admin access along as feedback. I can’t provide implementation timelines or ongoing status updates, but I appreciate the detailed suggestion!

-Yash

---

<div class="post-metadata">

**Author:** ![yash.m](https://avatars.discourse-cdn.com/v4/letter/y/53a042/32.png) [@yash.m](https://community.openai.com/u/yash.m)\
**Post date:** [October 26, 2026, 11:14pm UTC](https://community.openai.com/t/feature-request-browser-device-flow-admin-login-for-openai-cli-and-terraform-pulumi/1395669/3 "2026-10-26T23:14:30Z")

</div>

Closed on October 26, 2026, 11:14pm UTC


