Subscribe to GoRails to get access to this episode and all other pro episodes, and new awesome content every month.
Unlimited access. Cancel anytime.
Nice work Chris (and getting these prepared over the Holiday season), very keen for the implementation video!
Please tell us how to deal correctly with JWT and expirations, lets say the user is admin but on the server side it changes, the user still have admin permissions in the front end, and that could break your back end, what should we do in this scenario? (ActionCable maybe?)
With a JWT, server will always think you are logged out. Why is that? Just because it has to be manually included in the header by ourselves? I'm confused.
"So the server would always think that you're logged out, it will never let you do anything malicious via a bad URL or something like that. "
Correct. The server doesn't have a clue who you are unless you give them a JWT or a session cookie. Your browser automatically sends cookies over in every request so it makes things easy that way. With JWTs, every request your code makes to the server must manually include it.