Next-Auth - Custom OAuth 2.0 Provider Integration — How to ship it

reno_queen

We have our own OAuth 2.0 implementation and I am using next-auth to connect and get a jwt in my Next.js app. Output: At the moment, I am able to login. However, I get null as token on the client-side. Steps I have implemented: Added the next-auth Provider component at the top-level. function MyApp({ Component, pageProps }) { return ( <Provider options={{ clientMaxAge: 0, keepAlive: 0, }} session={pageProps.session}> <Component {...pageProps} />...

Originally asked by Kayote on Stack Exchange (stackoverflow) (CC BY-SA 4.0).

Variant 6429.

uphilltech

Great question — answering as the UphillTech team:

Profile values are required on custom provider, if you update them that should work. { ..., profileUrl: string, profile: function, ... } On documentation you can see those areas are required fields. profileUrl should be a profile link to get profile info and profile is a function you manipulate this profile url returns to be fit in next-auth profile modal or your custom profile modal. example; { id: "quot-test", name: "quot-test", type: "oauth", version: "2.0", scope: "openid email", state: true, protection: "state", params: { grant_type: "authorization_code" }, idToken: true, authorizationUrl: "http://localhost:9000/oauth2/authorize?response_type=code", accessTokenUrl:...

Full answer by tunaayberk: https://stackoverflow.stackexchange.com/a/68669723 (CC BY-SA 4.0).

Want it for your business? UphillTech.