Answers

1. Adding unique constraints directly on a database ensures that this standard is enforced, no matter whether data manipulation is done via migration or a server request. This also protects us from corrupting data if a new feature is added at another endpoint that forgets to enforce this standard, or if the code is altered in later alterations of the endpoints.
2. If an attacker manages to obtain a JWT, it does not mean that they have direct access to the user’s password. Also, if the tokens get refreshed, then the access the attacker has to items has a limited timeframe.
3. The JWT can be stored in local HTML storage or cookies.
4. We can store multiple data points in the token when hashing it. Therefore, we can encrypt the user ID. With this, we can extract the user ID for operations related to the to-do item’s creation, deletion, or edit.
5. We return an HttpResponse struct with HTML/text body that contains a string housing a couple of HTML tags. In between...