I’m working in a deployed test environment for the sake of implementing OAuth. Both my authentication and authorization endpoints are wrappers on Google OAuth - the authentication endpoint just redirects to google, and the authorization endpoint makes the post call to google itself for the sake of retrieving the refresh token. Without the auth body, the plugin manifest loads up and gets verification no problem. But when I add the following json body,
submitting the plugin’s url to “develop your own plugin” fails. I assume there are expectations with the auth client implementation, particularly as to what the first request to the authentication URL is, but I can’t track down what the issue could be. My Auth service gets no requests when I tell chatgpt to fetch the manifest, and my actual plugin’s endpoint just returns 200 responses to the ai-plugin.json requests. Any pointers would be appreciated!
I don’t think you will receive a request on the oauth endpoint at the moment OpenAI gets your manifest. So this is expected behavior.
But at the sept after, once manifest is validated, it will ask you to add an extra verification_token property to the manifest with a value given by OpenAI.
And once that’s done and verified, it will trigger the oauth flow to install the plugin in your conversation.
This manifest works perfectly for validation when I set auth to none: I’m able to use my test plugin, see the validation results, go through the typical no-auth flow and messaging. But when I add the Oauth data, it generates the following message.
That could be part of it. Ultimately I used PluginLab, but before I reached that point I found some success by having the auth URL within the same domain as my manifest. That doesn’t seem the be the core problem though, seeing as with Pluginlab the auth URL is entirely different.
Maybe you could try to set "authorization_content_type" from "application/json" to "application/x-www-form-urlencoded"? The post (https: // community.openai. com /t /oauth-token-request-failures-msal/211344) succeeded to login through the plugin installation process, but got “Couldn’t log in with plugin” inside the chat.