Tags: net head. com not fully decrypted Shu get www encryption and decryption
User login, backend generate token back to front end
The front end gets token, and each time login uses the token in the header for permission verification
The backend receives tokens from the front end, and is validated against the token by a database or Redis or session.
The backend receives tokens from the front end, and if it is through a set of cryptographic decryption algorithms to determine whether the user's identity is legitimate, this way for JWT
The front-end does not encrypt and decrypt the processing, just use a carrier to save tokens, this token is to decrypt the authentication or through the database is better, are back-end self-throw self-connected
Maybe it's not exactly right now, just record it.
Token token and JWT