Re:Things you should know about Token-based Authentication
by woloski on Tuesday January 28, 2014 @12:04PM
(#7138193)
Yes, that's correct.
Re:Things you should know about Token-based Authentication
by arethuza on Tuesday January 28, 2014 @12:18PM
(#7138293)
So to get the advantages of the JWT approach you really have to trust the content of the tokens you receive - if you start validating everything and scrutinizing the claims made in detail (especially against a database table of issued tokens) you might as well use an opaque bearer token?
Re:Things you should know about Token-based Authentication
by woloski on Tuesday January 28, 2014 @12:28PM
(#7138357)
Yes, I don't think there is a one-size-fits-all answer. It will depend on your use cases. You can always start small using JWT and move to database backed tokens when you get a better idea of your architecture, use cases and authorization needs. For the user, it will still be opaque and bearer.
With opaque bearer tokens you effectively have the same claims but these are stored on the server (e.g. in a database) and keyed by the opaque token value. The claims never leave the server.
Is that roughly correct?