authenticationrestful-authenticationjwt

Where do I need to use JWT?


The structure and protocol aside, I was wondering where JWT fits into client/server communication?


Solution

  • What JWT is exactly?

    It is a token that only the server can generate, and can contain a payload of data.

    What's the point of it?

    A JWT payload can contain things like user ID so that when the client sends you a JWT, you can be sure that it is issued by you, and you can see to whom it was issued.

    Where can it be useful?

    Usually, in RESTful APIs, where the server must not use any sort of sessions.

    How does it differ from using sessions?

    What is a typical authentication flow using JWT?

    Jwt contains the encoded form of the algorithm.data.signature and so if the user tries to fiddle with the user ID or any other data held in the jwt, then the jwt signature becomes invalid.

    Jwt is encoded (not encrypted), so any one can read the data component of the jwt (see jwt.io for example). Therefore it is recommended not to store any secrets like password in the jwt.

    It is also recommended to use an encrypted connection (SSL/TLS) when making the web request that contains the jwt because otherwise an attacker can steal the jwt and use it to impersonate you.