5 ms·

> I'd pay for it even if it was just empty repo => dumb site w/ user auth Never understood what is so hard with user auth and why people need an example of a S

by aikah 10y ago

> I'd pay for it even if it was just empty repo => dumb site w/ user auth Never understood what is so hard with user auth and why people need an example of a SPA with user auth. Your server is just a web API, so just use stateless authentication.

bitdeveloper 10y ago
I think it's mostly because getting it wrong is a Pretty Big Deal, so people aren't sure if they can trust themselves and the scheme they came up with.
- deleted 10y ago
  [deleted]
delinka 10y ago
The tutorials/instructions I've see never address the reasons for the authors' decisions, and any alternative packages or approaches that might be considered by the reader. Informing should also be a goal rather than simply providing a recipe. The reasons for these decisions would go a long way to addressing the concerns bitdeveloper has, too.
- wwalser 10y ago
  I'll be writing up my own experience building auth for askinline.com. I don't know how to keep you in the loop other than saying to follow me on Medium or Twitter. It's a React + Redux front end with Hapi + Sequelize backend. It uses JWTs in local storage for authentication (that decision will take some defending since it most applications should store it in a cookie) and sometimes uses single uses JWTs for things like email verification. I'm planning to write up how we do Google Login, password based signup and login including email verification and initial load decisions tree for dashboard or login page.
  - hawkweed 10y ago
    "most applications should store it in a cookie" Why do you think that most application should store JWT token in the cookie? Both approaches have their pros/cons.
    - wwalser 10y ago
      Cookies have several security features built in and if all you're storing is a session identifier they are generally better than a JWT from a size perspective. This does a better job that I'm going to try for in a HN comment: http://cryto.net/~joepie91/blog/2016/06/13/stop-using-jwt-for-sessions/ http://cryto.net/~joepie91/blog/2016/06/13/stop-using-jwt-fo...

by aikah 10y ago

bitdeveloper 10y ago

I think it's mostly because getting it wrong is a Pretty Big Deal, so people aren't sure if they can trust themselves and the scheme they came up with.

deleted 10y ago
[deleted]

delinka 10y ago

The tutorials/instructions I've see never address the reasons for the authors' decisions, and any alternative packages or approaches that might be considered by the reader. Informing should also be a goal rather than simply providing a recipe. The reasons for these decisions would go a long way to addressing the concerns bitdeveloper has, too.

wwalser 10y ago
I'll be writing up my own experience building auth for askinline.com. I don't know how to keep you in the loop other than saying to follow me on Medium or Twitter. It's a React + Redux front end with Hapi + Sequelize backend. It uses JWTs in local storage for authentication (that decision will take some defending since it most applications should store it in a cookie) and sometimes uses single uses JWTs for things like email verification. I'm planning to write up how we do Google Login, password based signup and login including email verification and initial load decisions tree for dashboard or login page.
- hawkweed 10y ago
  "most applications should store it in a cookie" Why do you think that most application should store JWT token in the cookie? Both approaches have their pros/cons.
  - wwalser 10y ago
    Cookies have several security features built in and if all you're storing is a session identifier they are generally better than a JWT from a size perspective. This does a better job that I'm going to try for in a HN comment: http://cryto.net/~joepie91/blog/2016/06/13/stop-using-jwt-for-sessions/ http://cryto.net/~joepie91/blog/2016/06/13/stop-using-jwt-fo...