API Platform locked by university domain SSO enforcement — ChatGPT login still works, only API Platform blocked

API
1

Posting in case any staff can help route a support case that’s stuck at Tier 1.

My API Platform account (~$2000 in credits, registered under my former university email) got locked out last week after the university enabled domain-verified SSO on the API Platform. I’m alumni and not in their IdP access group, so SSO cannot complete. Error UUID on the login page: ce5c4839-d1b7-4589-85ef-22e553b9652a.

Curious/useful detail: I can still log into ChatGPT and this forum via Google on the same linked Google account — the block is specifically on platform.openai.com. So the university enforced SSO on the API Platform side of the domain only, not ChatGPT. My Google-linked identity is clearly still intact on OpenAI’s side.

I have an open support case (07997404) but the Tier 1 responder has so far treated it as a browser troubleshooting issue, then as a credit transfer request — neither of which is what I’m asking for. What I actually need is either:

  1. Change the primary email on the API Platform account from my university email to my personal Gmail, so the account falls outside the SSO-enforced domain.
  2. Or, exempt my individual account from the domain SSO enforcement.

Both are account-level actions support can perform. I can verify ownership via invoices, payment method, org ID, or API logs.

Is there a staff member who can route this to the right team, or anyone who’s resolved a similar SSO lockout and knows the path?

Thanks.

2

Welcome to the dev community! @zanwenfu

It sounds like this may be more about which login path is being triggered rather than the account itself.

In some cases, certain login methods (like entering an email first or using SSO) can automatically route you through a specific authentication flow that won’t complete successfully depending on how the account is set up. That can make it look like the account is blocked, when it’s really just the wrong login path being used.

If your account is linked to a social login (like Google), it’s worth trying that route directly instead of entering your email or going through any SSO option.

A few things that can help:

  • Start from a fresh session (incognito/private window)
  • Go straight to login and pick the social login option first
  • Avoid entering the email beforehand, as that can trigger a different flow

If that works, it would suggest the account itself is still accessible and it’s just a routing issue during sign-in. Hope this helps narrow it down a bit.

~Smith