---
title: "Comment by Songs Le on \"Authentication for Next.js using Firebase\" | Hashnode"
description: "There&#39;s no server side auth present in this article btw. The one you mentioned at the last is only for validating apis. So, auth on nextjs pages still rende"
url: "https://hashnode.com/posts/authentication-for-nextjs-using-firebase/5f85a7f100106b423de17f09/comment/5f897975d7dc0b17a97a1f07"
---

[Discussion](https://hashnode.com/posts/authentication-for-nextjs-using-firebase/5f85a7f100106b423de17f09)

Comment [Authentication for Next.js using Firebase](https://hashnode.com/posts/authentication-for-nextjs-using-firebase/5f85a7f100106b423de17f09)

[Songs Le](https://hashnode.com/@songsle)

[Oct 16, 2020](https://hashnode.com/posts/authentication-for-nextjs-using-firebase/5f85a7f100106b423de17f09/comment/5f897975d7dc0b17a97a1f07)

There's no server side auth present in this article btw. The one you mentioned at the last is only for validating apis. So, auth on nextjs pages still rendered on client side. Only solution as given by firebase auth is to use service-worker or to create cookies. Btw, very good article. It's a clean code.

[Corey O'Donnell](https://hashnode.com/@CodeByCorey)

[Oct 16, 2020](https://hashnode.com/posts/authentication-for-nextjs-using-firebase/5f85a7f100106b423de17f09/comment/5f897975d7dc0b17a97a1f07#reply-5f89b624d7dc0b17a97a2210)

Maybe I should have labeled it as API authentication and not server-side.

The reason I did not include it is that I felt the redirect was more than enough.

Performing a redirect on the server is not fully supported by Next.js causing a total reload since it is not using Next.js's router.
