I’m getting weird behavior with OAuth in my Actions. I’ve got endpoints that generate valid tokens and return the required JSON, but once I’ve gone through the OAuth process, ChatGPT just loops endlessly, never actually accessing any functions, and eventually (after a few seconds) exhausting my GPT-4 quota. I get no error information.
Anyone seen anything like this? I’ve got nothing to work with to figure out what’s happening. The token generation on my backend works fine, and the generated tokens are valid, but once generated ChatGPT just spins.
I wonder of perhaps my OpenAPI is misconfigured? What should
components.securitySchemes be, for example? I’m assuming, perhaps naively, that it remains
BearerAuth: # arbitrary name for the security scheme
This is how my endpoints all actually work, and how the existing OpenAPI spec for them is configured. A token is acquired by the client, and then used for access. I assume that’s what the GPT’s Actions are doing: OAuth is used to get a token and that is used according to the
ecuritySchemes as http/bearer (like any other access to my endpoints).