All threads / JSON Web Tokens (JWT) vs Rails Session Cookies Discussion

Ask A Question

Notifications

You’re not receiving notifications from this thread.

JSON Web Tokens (JWT) vs Rails Session Cookies Discussion

Nice work Chris (and getting these prepared over the Holiday season), very keen for the implementation video!

Reply

Great material. Can't wait for the implementation using JWT.

Cheers

Reply
Masud Rana Hossain ·

Loving these advanced topics! Keepem coming, Chris!

Reply

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?)

Reply

Excellent general overview of JWT vs session. Can't wait for the hands-on with JWT.

Reply

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.

Reply

the second half of the video is really hard to understand for me.

Reply
Join the discussion

Want to stay up-to-date with Ruby on Rails?

Join 34,674+ developers who get early access to new tutorials, screencasts, articles, and more.

    We care about the protection of your data. Read our Privacy Policy.

    logo Created with Sketch.

    Ruby on Rails tutorials, guides, and screencasts for web developers learning Ruby, Rails, Javascript, Turbolinks, Stimulus.js, Vue.js, and more. Icons by Icons8

    © 2020 GoRails, LLC. All rights reserved.