Replies: 81 comments 5 replies
-
|
Made some updates and wrote notes regarding providers that will be difficult / impossible for us to manually test. I'll manually try some of the additional ones for which we have clientId's / secrets soon 👍 |
Beta Was this translation helpful? Give feedback.
-
|
Anyone reading this, if you use any of the built-in providers, we would highly appreciate your help making sure that those will work in the future! Until now, we haven't enforced anything at all, and so some built-in providers might have never even worked properly... Please leave a comment here if you find an issue or have anything related to say! 🙏 💚 |
Beta Was this translation helpful? Give feedback.
-
|
Hi, @lluia . I'm trying to integrate nextjs with azure ad. After detailed check, I think the issue is at auth step where to "scope" is always set to "openid" rather than the one defined in doc which should be 'offline_access User.Read' This scope 'openid', the get user function does not have enough permission to retrive user information with graph api /me and always generate 403. I'm not expert on either aad or next-auth so I can hardly sure if this is a bug or something wrong with my setting but I have tried to force the scope to 'offline_access User.Read' which makes it work. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @lluia, I´m trying to upgrade Next-auth import NextAuth from 'next-auth';
import CognitoProvider from 'next-auth/providers/cognito';
export default NextAuth({
providers: [
CognitoProvider({
clientId: process.env.COGNITO_CLIENT_ID,
clientSecret: '',
domain: process.env.COGNITO_DOMAIN,
issuer: `https://${process.env.COGNITO_DOMAIN}/`
})
],
callbacks: {...}
});
After a little research, this error is not in your library, it is due to a dependence library |
Beta Was this translation helpful? Give feedback.
-
|
@javigonz you should set the client's token endpoint auth method to none, not your client secret to an empty string. That's the very much intended state. Whether next-auth abstracts setting the method to none for you or exposes a client auth property is out of openid-client Lin's control. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah @panva, probably that the key, add a way to set this token endpoint auth method into https://next-auth.js.org/configuration/providers/oauth-provider#options |
Beta Was this translation helpful? Give feedback.
-
|
Going to expose further options through #2717, I'll just test it out locally. |
Beta Was this translation helpful? Give feedback.
-
|
@javigonz could you test out? #2717 (comment) Check the new |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Testing the EVE Online integration, I receive the following error from EVE's login server: If I update the scope in the URL to After investigating further and testing myself, I got it working with an updated provider where I specified the authorization property in the default parameters for the provider. I opened a PR with these changes, where I also rewrote the EVE Provider in TypeScript. |
Beta Was this translation helpful? Give feedback.
-
|
Hi! Thanks so much for what is shaping up to be an excellent library. I'm testing I first referenced the documentation for this provider, but using this config provided a successful response for me: |
Beta Was this translation helpful? Give feedback.
-
URL still only has |
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
-
|
I just set up a Salesforce with NextAuth using the example: // /api/auth/[...nextauth].ts
import NextAuth from "next-auth/next";
import SalesFoceProvider from "next-auth/providers/salesforce";
export default NextAuth({
debug: true,
secret: "NEXTAUTH_SECRET",
providers: [
SalesFoceProvider({
clientId: "SALESFORCE_CLIENT_ID",
clientSecret: "SALESFORCE_CLIENT_SECRET",
},
}),
],
});But got stuck at this callback error: I added scope as an authorization parameter and now the login flow is working. // /api/auth/[...nextauth].ts
import NextAuth from "next-auth/next";
import SalesFoceProvider from "next-auth/providers/salesforce";
export default NextAuth({
debug: true,
secret: "NEXTAUTH_SECRET",
providers: [
SalesFoceProvider({
clientId: "SALESFORCE_CLIENT_ID",
clientSecret: "SALESFORCE_CLIENT_SECRET",
authorization: {
params: {
scope: "api id web",
},
},
}),
],
}); |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for reporting that back to us @squeezeday! I'll make sure to add it to the docs. |
Beta Was this translation helpful? Give feedback.
-
|
EVEOnline provider not working in v4 .... The problem is that a Scope query parameter is being inserted in the URL which EVE Online is reporting as invalid (Invalid scope). The scope parameter needs to be removed or set to blank (example: ..&scope=&..) See bug report #3760 Also some additional information ... even removing the Scope parameter manually it allows you to authenticate with EVE Online, however in the callback Next-Auth throws a OAuthCallbackError error:
It seems that EVE Online does not return an id_token which next-auth is expecting? When you get and use the code returned to get the access token, you get a response that looks like this from EVE Online:
Could it be that Next-Auth is expecting id_token and not access_token ? Update: Changing the EVE Online application type from Authentication Only to Authentication & API Access and adding the publicData scope, it now successfully redirects you to the EVE Online login screen. However I am now receiving a OAUTH_CALLBACK_ERROR saying the id_token is not present in TokenSet?
So only error still remaining is the id_token ? EDIT: Interesting enough the access_token returned is a JWT token ... the payload data in the token includes the following:
So to get the returned user data for NextAuth. All we need is the access_token as it contains the character name and character id which is all we need. So the flow should be:
Would the above be easy to implement with NextAuth? |
Beta Was this translation helpful? Give feedback.
-
|
@mckernanin are you able to comment on my post above please? |
Beta Was this translation helpful? Give feedback.
-
|
@balazsorban44 and I worked through it a bit, CCP does some non-standard stuff which is annoying. The provider that I'm successfully using in an app of mine looks like this: function EVEOnlineUpdated<P extends Record<string, any> = EVEOnlineProfile>(
options: OAuthUserConfig<P>
): OAuthConfig<P> {
return {
id: "eveonline",
name: "EVE Online",
type: "oauth",
wellKnown: "https://login.eveonline.com/.well-known/oauth-authorization-server",
authorization: {
params: {
scope: "publicData esi-planets.manage_planets.v1",
},
},
idToken: true,
profile(profile: P) {
const characterId = profile.sub.split(":")[2];
return {
id: characterId,
name: profile.name,
ownerHash: profile.owner,
email: null,
image: `https://image.eveonline.com/Character/${characterId}_128.jpg`,
};
},
token: {
async request({ client, provider, params, checks }) {
const tokens = await client.oauthCallback(provider.callbackUrl, params, checks);
tokens.id_token = tokens.access_token;
return { tokens };
},
},
options,
};
}The custom token callback copies access_token to id_token |
Beta Was this translation helpful? Give feedback.
-
|
@mckernanin thank you for the above code. I've now created a custom provider and the SSO login now works! I now have an issue getting the user details from the session? I'm using the following in my component:
however, session.user.id is not defined? I'm also getting session cookie length errors: Am I missing something here? |
Beta Was this translation helpful? Give feedback.
-
|
Yeah so it seems like you're trying to store too much in the cookie (in the jwt callback?), which then therefore cannot be read back out in the following callback functions, thats probably why your See the warning right above the start of this section: https://next-auth.js.org/configuration/callbacks#session-callback |
Beta Was this translation helpful? Give feedback.
-
|
Ah ok thanks! I changed my callback to just include the account and user information as follows:
The reason why I did the if (token.token.user) is because the callback seems to be executed twice so only want to make one modification to it. I'm not sure if that is the correct approach or not ... then in the session callback, I did the following:
(yes, I need to fix the double session object) It works ... but seems messy :( UPDATE: Actually, I don't need to duplicate the session information - the information is there, just in a different section so I don't need to copy it etc. |
Beta Was this translation helpful? Give feedback.
-
I followed this code to get name and email from profile but id_token is overwritten and I cannot get id_token again where I need at the federated_logout. Any work around to save raw id_token? |
Beta Was this translation helpful? Give feedback.
-
|
Just verified the Coinbase Provider is working correctly with the latest version of NextAuth 💚, when well configured...
|
Beta Was this translation helpful? Give feedback.
-
|
Atlassian is giving me some cryptic internal error in the latest version. Perhaps it should be removed - or a note should be added to the docs? |
Beta Was this translation helpful? Give feedback.
-
|
Did you every manged to get something working with Atlassian? |
Beta Was this translation helpful? Give feedback.
-
|
Mailchimp (similar to EVEOnline above) was returning I'm now getting an OAuthCallbackError: |
Beta Was this translation helpful? Give feedback.
-
|
I'm getting this error when using instagram provider. "response" body "token_type" property must be a non-empty string here's sample response json returned by instagram {
access_token:"some long string",
user_id:123123123
} |
Beta Was this translation helpful? Give feedback.
-
|
same here |
Beta Was this translation helpful? Give feedback.
-
|
https://github.com/emilaleksanteri/igauthtest issue recreated here |
Beta Was this translation helpful? Give feedback.
-
|
same here |
Beta Was this translation helpful? Give feedback.
-
|
VK provider If you add user_id to default Schema.prisma, then everything works. P.S. VK no send mail before. The email address in provider was null. But now, we can add an email address in settings. But then we get another error I can’t figure out where the problem is, in the provider or the adapter |
Beta Was this translation helpful? Give feedback.
-
|
how to solve this problem with auth vk |
Beta Was this translation helpful? Give feedback.
-
|
I had the same issue getting token from Figma. Found a solution with the WeChat provider and it worked for me. Maybe try something similar for VK (haven’t tested it): token: {
url: `https://oauth.vk.com/access_token?v=${apiVersion}`,
async conform(response: Response) {
const data = (await response.json()) as Record<string, unknown>
return Response.json({ ...data, token_type: "bearer" }, response)
},
}, |
Beta Was this translation helpful? Give feedback.
and others
-
Description 📓
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:
42AppleAtlassiancallback_url, internal error at AtlassianAuth0Azure B2CAzure ADBasecampBattleNetBoxBungieCognitoCoinbaseDiscordDropboxEve OnlineFacebookFaceITFourSquareFreshbooksFusionAuthGithubGitlabGoogleIS4InstagramKakaoKeycloakLineLinkedInMailChimpMailRuMediumNaverNetlifyOktaOneLoginOssoRedditSalesforceSlackhttpsfor redirect URLs, even for local development. UsedngrokSpotifyStravaTwtichTwitterVKWordpressWorkOSYandexZohoZoom@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
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
Beta Was this translation helpful? Give feedback.
All reactions