If SSO is enforced, but configured wrong - it will prevent login and cause a full DoS

ChatGPT
,
1

I accidentally set SSO enforced before testing the login with “enable SSO,” - and now I am unable to access the account. I also am unable to update any billing or profile settings within my account. I have had a ticket opened for almost a week. Any recommendations on a way to turn off the “enforce SSO” flag?

2

I think problem is much more than that

Access to fetch at ‘https:// chatgpt. com/public-api/get_user_connection_info?email=YYYYYYYYY&client_id=XXXXX’ from origin ‘https:// auth.openai. com’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. If an opaque response serves your needs, set the request’s mode to ‘no-cors’ to fetch the resource with CORS disabled.Understand this errorAI
datadog.client-D4M9wJO3.js:7

  GET https://chatgpt.com/public-api/get_user_connection_info?email=YYYYYYYYY&client_id=XXXXX net::ERR_FAILED 403 (Forbidden)

(anonymous) @ datadog.client-D4M9wJO3.js:7
a @ datadog.client-D4M9wJO3.js:7
queryFn @ route-wOfdhi3G.js:2
p @ route-wOfdhi3G.js:2
h @ route-wOfdhi3G.js:2
(anonymous) @ route-wOfdhi3G.js:2Understand this errorAI
authorize:1 Access to fetch at ‘https:// chatgpt. com/public-api/get_user_connection_info?email=YYYYYYYYY&client_id=XXXXX’ from origin ‘https:// auth.openai. com’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. If an opaque response serves your needs, set the request’s mode to ‘no-cors’ to fetch the resource with CORS disabled.Understand this errorAI
datadog.client-D4M9wJO3.js:7

  GET https://chatgpt.com/public-api/get_user_connection_info?email=YYYYYYYYY&client_id=XXXXX net::ERR_FAILED 403 (Forbidden)

(anonymous) @ datadog.client-D4M9wJO3.js:7
a @ datadog.client-D4M9wJO3.js:7
queryFn @ route-wOfdhi3G.js:2
p @ route-wOfdhi3G.js:2
h @ route-wOfdhi3G.js:2
(anonymous) @ route-wOfdhi3G.js:2
Promise.then
(anonymous) @ route-wOfdhi3G.js:2
Promise.catch
h @ route-wOfdhi3G.js:2
(anonymous) @ route-wOfdhi3G.js:2Understand this errorAI
datadog.client-D4M9wJO3.js:13 TypeError: Failed to fetch
at datadog.client-D4M9wJO3.js:7:121755
at a (datadog.client-D4M9wJO3.js:7:121522)
at Object.queryFn (route-wOfdhi3G.js:2:39916)
at Object.p [as fn] (route-wOfdhi3G.js:2:12798)
at h (route-wOfdhi3G.js:2:7536)
at route-wOfdhi3G.js:2:8141
Qt. @ datadog.client-D4M9wJO3.js:13
onError @ route-wOfdhi3G.js:2
u @ route-wOfdhi3G.js:2
(anonymous) @ route-wOfdhi3G.js:2
Promise.catch
h @ route-wOfdhi3G.js:2
(anonymous) @ route-wOfdhi3G.js:2
Promise.then
(anonymous) @ route-wOfdhi3G.js:2
Promise.catch
h @ route-wOfdhi3G.js:2
(anonymous) @ route-wOfdhi3G.js:2Understand this errorAI

3

I have had a ticket open for some time, but any suggestions on how to fix this?

4

The help desk was able to turn off “enforce SSO” - issue has been resolved - Thank you help desk team!