Manually Test Providers (v4)
See original GitHub issueDescription π
Before the release of v4 we want to manually test most (if not all) the current OAuth providers to make sure the changes that happen on v4 to their configuration didnβt break any of them π€π½
We also havenβt enforced any kind of testing prior to v4, so there is a big chance that some providers do not even work in v3, which might have gone undetected if there was no interest from users to open issues.
Hereβs the table where we keep track of this testing:
Provider | Account created | Manually tested | Comments |
---|---|---|---|
42 |
β | β | #3189, tested by @estarossa0 |
Apple |
β | β | #2875. Thanks @sergeymishin and @TheoBr for the help! See https://github.com/nextauthjs/next-auth/pull/2875#issue-747917222 for caveats |
Atlassian |
β | π¨ | Not able to redirect back to callback_url , internal error at Atlassian |
Auth0 |
β | β | |
Azure B2C |
β | β | #2862, @BenjaminWFox provided me test account/client. We could not retrieve a profile picture |
Azure AD |
β | β | Fixed in #2818, @ndom91 has the account for this to test. Default profile picture size is 64x64 #2910 |
~Basecamp ~ |
β | β | Removed see, https://github.com/nextauthjs/next-auth/pull/511#issuecomment-892079767 |
BattleNet |
N/A | ||
Box |
N/A | ||
Bungie |
|||
Cognito |
β | β | #2829, AWS provided by @s-kris |
Coinbase |
N/A | ||
Discord |
β | β | |
Dropbox |
β | ||
Eve Online |
|||
Facebook |
β | β | |
FaceIT |
β | ||
FourSquare |
β | β | |
Freshbooks |
β | ||
FusionAuth |
β | #3376 by @alessandrojcm | |
Github |
β | β | |
Gitlab |
β | β | |
Google |
β | β | |
IS4 |
β | β | |
Instagram |
β | ||
Kakao |
β | ||
Keycloak |
β | β | #2485, #2851 |
Line |
β | β | #2917, email needs special setup. tested by @ThangHuuVu |
LinkedIn |
β | β | #2821 |
MailChimp |
β | ||
MailRu |
|||
Medium |
|||
Naver |
|||
Netlify |
|||
Okta |
β | β | #2856 |
OneLogin |
β | β | |
Osso |
|||
Reddit |
|||
Salesforce |
|||
Slack |
β | β | Fixed in #2848. Requires https for redirect URLs, even for local development. Used ngrok |
Spotify |
β | β | |
Strava |
|||
Twtich |
β | β | |
Twitter |
β | β | |
VK |
|||
Wordpress |
|||
WorkOS |
β | β | WIP #3886 thanks @m-abdelwahab for the infra support |
Yandex |
|||
Zoho |
|||
Zoom |
@balazsorban44 @ndom91 if you could mark the ones you have already manually tested and verified theyβre working so we can know which ones are left to test ππ½
Notes
- BattleNet requires Battle.net Authenticator (possibly replaceable via their first-party app. This is different from normal TOTP)
- Box only has paid plans
- Coinbase requires to know your customer (KYC) verification via video chat like when opening a bank account
The relevant PR making this required is #2411. Checks its description for more info.
The documentation page here might also be useful: https://next-auth.js.org/configuration/providers/oauth-provider#options
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:76 (42 by maintainers)
Hi everyone.
Working on a new project, ran into issues with 2 providers, here are the details.
I created brand new accounts for each one of them, then configured new apps.
I can confirm he Yandex provider works well.
The error I get with VK (CALLBACK_OAUTH_ERROR):
The error I get with Mail.ru (OAUTH_CALLBACK_RESPONSE):
Please let me know how I can help, I can help submit a PR, but Iβm unsure how to fix the issues. Is there a way to debug provider callbacks?
@insik-han I also face same issue and created a PR
Or other solution you can try right now pages/api/auth/[β¦nextauth].ts