nookies VS react-keycloak

Additionally, you can take this a step further and store the JWT inside of a cookie. With this, instead of authenticating users on each request made on every Next.js page, you can first check if this JWT cookie is present. If it is not present, then you can proceed to authenticate the user. This is quite similar when building a login functionality. You will be using a third-party package called Nookies to implement this functionality.

Should I use cookies using a package like nookies or just stick to local storage? I do not want a flash of style. What do you usually use for situations like this?

When the user submits the login form, you send an API request with their user/password. Your API handles it however you wish, and on success returns a user token. Using cookies (I've found the nookies library helpful for dealing with cookies), save that token locally, and then send that token along with every API request.

I am creating a nextjs app and am using Keycloak for login and sessions. I am using the (@react-keycloak/ssr)[https://github.com/react-keycloak/react-keycloak/tree/master/packages/ssr] library, but have questions about how the access token is used.

2- Connect Keycloak to your SPA directly using a generic OpenId Connect client or react-keycloak. This way Keycloak will secure 2 clients separately (frontend(s) and Nestjs)