<![CDATA[NextJS + custom backend (NestJS)]]>Hi folks,

I've been reading https://fusionauth.io/docs/quickstarts/quickstart-javascript-nextjs-web and then I realized that it is communicating directly with FusionAuth. Which means that we where providing it our client secret. I am cool with that idea however I was wondering if that does mean that I can now wipe out my backend RESTful APIs since they are not needed anymore. I mean I can keep them or at least the ones for mobile.

But in general I was not sure anymore about these endpoints.

I guess it boils down to whether I need full control over generating JWT tokens and things like that. Or maybe I am missing some points 🤔.

I also loved the @fusionauth/react-sdk but like I mentioned it is not working and I dunno how to fix it either. I appreciate it if you could help me with that too.

]]>https://fusionauth.io/community/forum/topic/2679/nextjs-custom-backend-nestjsRSS for NodeFri, 13 Mar 2026 05:03:22 GMTTue, 14 May 2024 10:21:06 GMT60<![CDATA[Reply to NextJS + custom backend (NestJS) on Mon, 20 May 2024 23:48:25 GMT]]>@kasir-barati When you say "I dunno if we can use them to change what Get /me endpoint returns", you might want to check out the UserInfo Populate Lamba.

]]>https://fusionauth.io/community/forum/post/7288https://fusionauth.io/community/forum/post/7288Mon, 20 May 2024 23:48:25 GMT<![CDATA[Reply to NextJS + custom backend (NestJS) on Sat, 18 May 2024 09:28:44 GMT]]>Thanks @mark-robustelli for your pointers, although I know how we can leverage lambda functions to customize our JWT tokens but I dunno if we can use them to change what GET /me endpoint returns. That's part of the reason I opt to develop my own backend to communicate with FusionAuth.

]]>https://fusionauth.io/community/forum/post/7279https://fusionauth.io/community/forum/post/7279Sat, 18 May 2024 09:28:44 GMT<![CDATA[Reply to NextJS + custom backend (NestJS) on Fri, 17 May 2024 21:50:44 GMT]]>@kasir-barati It depends on what you are trying to do. If you are trying to authenticate a user for your application and the login flow that redirects to FusionAuth and returns to your application works, then you would not need the APIs. Even if you need to customize the JWT, I would look into lambdas for that.

]]>https://fusionauth.io/community/forum/post/7275https://fusionauth.io/community/forum/post/7275Fri, 17 May 2024 21:50:44 GMT<![CDATA[Reply to NextJS + custom backend (NestJS) on Thu, 16 May 2024 21:33:57 GMT]]>We have an open issue for it in @fusionauth/react-sdk: https://github.com/FusionAuth/fusionauth-javascript-sdk/issues/99. But it might not be the answer if you are looking for an answer that utilizes next-auth.

]]>https://fusionauth.io/community/forum/post/7269https://fusionauth.io/community/forum/post/7269Thu, 16 May 2024 21:33:57 GMT<![CDATA[Reply to NextJS + custom backend (NestJS) on Tue, 14 May 2024 18:16:33 GMT]]>Like I mentioned before I tried the docs and I ended up with another bump along the way. It seems like FusionAuth integration with NextJS is not the best idea. Maybe it's time to switch gears and try SPAs 🤔?

]]>https://fusionauth.io/community/forum/post/7263https://fusionauth.io/community/forum/post/7263Tue, 14 May 2024 18:16:33 GMT<![CDATA[Reply to NextJS + custom backend (NestJS) on Tue, 14 May 2024 10:28:37 GMT]]>I've also read:

  1. https://fusionauth.io/community/forum/post/5781
  2. https://fusionauth.io/community/forum/post/5782

But none of them where what I needed. Though I jot down some comments there too 😃.

]]>https://fusionauth.io/community/forum/post/7256https://fusionauth.io/community/forum/post/7256Tue, 14 May 2024 10:28:37 GMT