Designing authentication and authorization for dashboard

[near valley]

Hey guys! I'm designing a dashboard based on next js 15 app router + sanity. Dashboard service is separate from main service on a subdomain.

My question: How would you protect a route when creating a dashboard? It is intended for use by only one user, aka admin. Is it worth setting up next-auth / other auth frameworks or would i be better off storing hashed password on sanity database?

[brazen geyser]

Post created!

🔎 This post has been indexed in our web forum and will be seen by search engines so other users can find it outside Discord

🕵️ Your user profile is private by default and won't be visible to users outside Discord, if you want to be visible in the web forum you can add the "Public Profile" role in id:customize

✅ You can mark a message as the answer for your post with Right click -> Apps -> Mark Solution
(if you don't see the option, try refreshing Discord with Ctrl + R)

[marsh quail]

Rolling your own auth is not recommended for a serious app. You can do it, but there are quite a few footguns to be aware of.

Check out https://authjs.dev/ and https://www.better-auth.com/docs/integrations/next