"Couldn't find manifest" on adding Oauth details

Hey all,

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,

auth: {
  type: "oauth",
  client_url: "https://auth.scholarai.io/authenticate",
  scope: "https://www.googleapis.com/auth/userinfo.email",
  authorization_url: "https://auth.scholarai.io/authorize",
  authorization_content_type: "application/json"
},

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!

1 Like

Even using pure google urls for OAuth, I get the same error:

auth: {
  type: "oauth",
  client_url: "https://accounts.google.com/o/oauth2/v2/auth",
  scope: "https://www.googleapis.com/auth/userinfo.email",
  authorization_url: "https://oauth2.googleapis.com/token",
  authorization_content_type: "application/json"
},

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.

Do you see any specific error?

You can see the deployed manifest here, for reference: https://test.scholar-ai.net/.well-known/ai-plugin.json

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.


The only messaging in the javascript console for searching the manifest is the following, which doesn’t give any guidance:

Let me know if you have any questions about implementing OAuth, happy to help with what I think is supposed to be the “correct” implementation lol

I second that question. I’m facing the same problem here.

I get “Couldn’t find manifest” after I add the OAuth details.

This might be just how you’ve copied it into the thread, but your auth object is not valid json.

All json keys must be strings. i.e. auth → “auth”, type → “type” etc.

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.

1 Like

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.