This is still an issue. No matter the user, role or permissions, we are unable to create access tokens. Multiple users at our organization report the same thing: after completing the auth flow to generate a token, they land back on the page with no token and the create a new token modal open.
In the same Business workspace and session, a Workspace Agents-only token creates immediately without verification. A Codex-scoped token—even Codex-only—gets POST /backend-api/wham/auth-credentials 401 and loops through MFA/SMS.
Hey @aron4, Codex tokens go through an extra verification step, which may explain why Workspace Agents tokens work in the same session. If this is for local CLI use, can you try codex login with ChatGPT? That avoids creating a token manually. Let us know if you need it for a script or CI job.
That link is meant to use Local computer access with Work Cloud. We don’t want to use Work Cloud.
A lot of people seem to be having this problem (not being able to create a Personal Access Token). There are a lot of reasons you might want to use a Personal Access Token, so this should just work.
Our use case is that we want to use Codex in a safe way by using a sandboxed environment. The Personal Access Token is used for credential injection.
As far as I understand, using another login method means that Codex will store login credentials inside the sandbox. We don’t think this is safe.
Please don’t sidestep the issue being described in this thread by suggesting using an entirely different auth mechanism. PATs are advertised and documented as a feature here: learn.chatgpt .com/docs/enterprise/access-tokens and yet they are entirely unusable due to this infinite MFA redirect loop that is affecting the 15+ people (and their organisations) in this thread. Coming off the back of DevDay (a supposed celebration of OpenAI collaborating with developers), brushing off this issue that has been open for over a month is disappointing.
Please either deprecate PATs officially or resolve the issue.
The issue seems to be fixed!
We got a reply from OpenAI support.
I can now create a PAT again. After phone verification, I did need to press create/continue again.
I tried again, but now the issue is with authentication itself – I am not getting the SMS, and when I ask for a resend I get a weird “Unable to send a text message to this phone number” message even though the form displays a correct working mobile number. Am I the only one?
This is a separate issue. Maybe make a new post for this?
(I’ve had this multiple times and it always worked when I tried again later.)
Seems that it was a temporary issue with the SMS OTP mechanism. This now works, and I confirm I was able to create PA; so the original issue seems to be resolved.