Custom provider not being called

[davedodea]

Hey team,

• A couple of days ago I set up a custom Linear provider and configured the details on Arcade dashboard.
• However when I attempt to auth a Linear tool - the call still seems to be directed to the "built-in" arcade-linear provider.
• I'v created several other custom providers, ie GitHUb, Notion etc, which all route auth calls to them as expected.

Any thoughts or more info I can share to help debug?

[torresmateo]

Hey @davedodea, are you using a custom user verifier for this, or Arcade's built-in verifier?

[davedodea]

Hey @torresmateo - yes, I've set up a custom verifier, which is working for other providers which I've created.

[nbarbettini]

@davedodea Can you share a screenshot of the details of the custom Linear provider you created? I agree that this should "just work" as you described.

Other info that's helpful:

• Do you have one custom Linear provider or multiple? I assume 1, but it never hurts to check 🙂
• Which tool(s) are you trying to call? (This will help me reproduce)

[davedodea]

Sure thing, see attached images.

• Just the 1 custom Linear provider.
• Tried calling both the GetIssue and GetTeam tools.

[nbarbettini]

Thanks! I was able to reproduce the issue. It's on our side - I'll make sure it gets fixed.

In your app/agent code, how are you calling the tools? If you can share a code snippet, I might be able to give you a workaround.

[nbarbettini]

Double post - try again, this provider should work for you now. I was able to apply a temporary workaround, but I still need to fix other providers that could be affected by the bug.

[davedodea]

Hey @nbarbettini - so when I call the following URL, provided by Arcade during an auth flow, I get:

• URL called: https://linear.app/oauth/authorize?actor=user&client_id=e6a5fa427dd75a0f158a2a9418ee5ee0&redirect_uri=https%3A%2F%2Fcloud.arcade.dev%2Fapi%2Fv1%2Foauth%2Fcallback&response_type=code&scope=read&state=5ce33ff7-cfd2-4046-8b66-b1b167e52b25

• parsed:

{
  "actor": "user",
  "client_id": "e6a5fa427dd75a0f158a2a9418ee5ee0",
  "redirect_uri": "https://cloud.arcade.dev/api/v1/oauth/callback",
  "response_type": "code",
  "scope": "read",
  "state": "5ce33ff7-cfd2-4046-8b66-b1b167e52b25"
}

• response: invalid redirect_uri parameter for the application.

• my custom Linear provider config in Arcade dashboard is indeed set to:
  https://cloud.arcade.dev/api/v1/oauth/callback

So, I enabled the option in the provider config to Use default redirect URI and it ensured the same value/URI was set in my Linear Oauth app.

However, when I re-triggered he auth flow, the auth URL from Arcade now points to a client id value that is not the one configured in my Linear provider in Arcade (guessing it is the default client id?):

{
  "actor": "user",
  "client_id": "e30e71e467f82b79f19916ee33b14b48",
  "redirect_uri": "https://cloud.arcade.dev/api/v1/oauth/f4c6b_aps_arcade-linear/callback",
  "response_type": "code",
  "scope": "read",
  "state": "50a76a24-b2ee-4f0f-b3f7-486a714cc4fb"
}

Resuling in the user bein authorized but through the default Linear provider, not my custom one, as expected.

[sdreyer]

@davedodea You should now be able to go to Providers -> Add OAuth Provider -> Included Providers -> Linear to use your own credentials. We're working on some fixes for the Custom Provider, but to point it towards linear, the id field needs to be set to linear

[davedodea]

Hey @sdreyer!
Thanks, I'll give this a shot in a few hours.
Does this mean any custom providers are not working at this time?

[davedodea]

but to point it towards linear, the id field needs to be set to linear

I take it you mean when configuring the "known"/included Linear provider that the id field needs to be set to linear OR do you mean when configuring a custom provider?

[nbarbettini]

Does this mean any custom providers are not working at this time?

@davedodea No, this was an issue specifically with Linear and Notion (the ones missing from the Included Providers dropdown).

I take it you mean when configuring the "known"/included Linear provider that the id field needs to be set to linear OR do you mean when configuring a custom provider?

The latter. There are two ways to configure a custom provider, if your goal is to have the built-in toolkits use that provider at runtime:

1. Pick one from the Included Providers dropdown and fill in the client ID and secret. Done!
2. If that is not an option for some reason, switch to the Custom Provider tab and fill in the full provider details. In this case (and only in this case), you need to set the ID field to linear (or google, slack, etc.) for the built-in toolkits to pick it up.

[nbarbettini]

Happy to dig deeper into your use case on a live call if you are not fully up and running!

[davedodea]

There are two ways to configure a custom provider, if your goal is to have the built-in toolkits use that provider at runtime:

Awesome! If this is not called out in the provider docs, I think it would be a solid addition. Unless I've missed it 🙈

[davedodea]

Happy to dig deeper into your use case on a live call if you are not fully up and running!

I'll attempt to get up and running following the above fixes/tips and then I might take you up on that offer!

[nbarbettini]

@davedodea For sure! Let us know how it goes.

[davedodea]

Update: The above worked flawlessly.

• configured new providers, using the "included" templates for both Lienar and Notion.
• made sure to use "linear", "notion" respectively for the id fields.
• removed previously created custom providers for both.
• re-ran auth flows for each.
  🎉 Worked first time.

Thanks @nbarbettini & @sdreyer for the help 👏

[nbarbettini]

Excellent, glad it's all working! Thanks for your patience @davedodea!