I can't personally think of a reason why using a JWT for a session would be objectively wrong.
JWT might be overkill a bit if you don't plan on sharing the session with another application or service, but I wouldn't consider it wrong.
Any encoded identifier that your application can use to determine who a "signed-in" user is should be fine. JWT falls in that group.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I can't personally think of a reason why using a JWT for a session would be objectively wrong.
JWT might be overkill a bit if you don't plan on sharing the session with another application or service, but I wouldn't consider it wrong.
Any encoded identifier that your application can use to determine who a "signed-in" user is should be fine. JWT falls in that group.