Skip to content

Conversation

@byrro
Copy link
Member

@byrro byrro commented Jan 5, 2026

It turns out that the OAuth2 class does not work when the provider has an Arcade well-known configuration and the user creates a custom OAuth provider. In order to work with well-known providers and custom OAuth providers, we must use the provider-specific class (e.g. auth.Slack), instead of OAuth2(id="arcade-slack").

This PR updates the current starter tools with an OAuth provider that has a specific class in Arcade's auth module. The remaining tools that have OAuth requirement but no specific class available, we changed the id from arcade-{provider}to just {provider}.

@byrro byrro requested review from a team, jottakka and torresmateo January 5, 2026 16:56
@byrro byrro self-assigned this Jan 5, 2026
@byrro byrro added the bug Something isn't working label Jan 5, 2026
@byrro byrro marked this pull request as ready for review January 5, 2026 17:15
@byrro byrro merged commit ea17a72 into main Jan 5, 2026
86 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants