-
Using nextjs 13.2.3 and next-auth 4.22.1. I setup a custom provider object to authenticate against a Oauth provider. After clicking on the provisioned button "Sign in with Custom Provider" I got a error message "Try signing with a different account". On the logs, I see an error as welll:
Based on the docs, the customer provider object does not have a 'client_id' property. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
Apparently property client_id is required in the object defining a custom provider. However, the correct label for the property is clientId. I added that to the object and the error is gone. |
Beta Was this translation helpful? Give feedback.
-
Same issue with my app, I just noticed switching between branches remove my env.local (which I manage via Vercel). If you have the same setup just pull your env Overall the problem looks like it can not find the |
Beta Was this translation helpful? Give feedback.
-
i have tried all the method you people mention above but none of them are ready to work so which others solution can be used? |
Beta Was this translation helpful? Give feedback.
Apparently property client_id is required in the object defining a custom provider. However, the correct label for the property is clientId. I added that to the object and the error is gone.