Portfolio project and authorization
Hi everyone, I'm facing this question. I'm writing a task list (ASP.NET API + React JS).
I'm wondering if I should implement registration and login (password reset), JWT, and authorization for roles.
I also have a question: if I implement login and registration, I'll need to reset the password, but what should I use for that?
And is it even worth doing all this if this project will be used in my portfolio, and I'll be gaining development experience from it?
1 Reply
It depends on your goals
You can store tasks in localstorage entirely without the need for a backend
But you can also store an anonymous session by giving the user a long lasting random UUID cookie or similar
If you decide to add auth, they'll have the benefit of re-authenticating across devices
And you also get a chance to e.g. sell different capabilities
If it's for a pet portfolio project, and you are not too familiar with authentication yet, that sounds like a good idea to me, just for the sake of gaining experience