Generate authorization URL server side?

[alessandrojcm]

Hi there, we're currently working on migrating our in-house authorization implementation to a third party solution (Fusionauth). For this we've decided to use next-auth for our application.

Now, we want this to be as transparent as possible for our users. Thus, we think that having a home page that just redirects to the OAuth provider would cause confusion. So my question is, is there a way of generating the authorization URL on getServerSideProps? (is this even a good idea?).

I know calling the /api/auth/signin/fusionauth endpoint directly from getServerSideProps won't work. By reading next-auth code, I can see that this is achieved by using the getAuthorizationUrl function, but this is not a public API. So, any ideas on how could we achieve this?

Thanks!

[balazsorban44]

Assuming you will have a custom provider, I would rather use

signIn("Id")

https://next-auth.js.org/getting-started/client#signin

You could start it from getServerSideProps also though

https://next-auth.js.org/getting-started/rest-api#post-apiauthsigninprovider

this might also be useful
#2621 (comment)

the returned url then can be visited with
the redirect option of getServerSideProps https://nextjs.org/docs/basic-features/data-fetching#getserversideprops-server-side-rendering

I wouldn't use getServerSideProps, only if it's absolutely necessary for your usecase though. What do you hope to gain by using it?

[balazsorban44]

I see. Yes, I believe I explained that usecase above as well.

Although it feels like a tiny blocking experience from the UX perspective IMO. you could do that session check client side in a useEffect or similar, and just show a skeleton ui while waiting. pretty similar how the vercel.com UI looks like.

(This is personal opinion though)

[alessandrojcm]

Alright thanks! To start the flow from getServerSideprops, how should I include the csrf token? As explained in #2621?

[balazsorban44]

https://next-auth.js.org/getting-started/client#server-side-example-1

be aware of the import (https://next-auth.js.org/getting-started/upgrade-v4)

I believe you could naively also find it in ctx.req.cookies somewhere.

[alessandrojcm]

Great thanks for your help, will take a look at that!

[balazsorban44]

keep me posted