---
title: "Discussion on \"JWT  Description\" | Hashnode"
description: "Discussion on \"JWT  Description\". Why “Bearer” Exists\nIn the early days, there were several types of authorization schemes, like:\n\nBasic — sends username and password encoded in base64\n\nDigest — uses hashed credentials\n\nBearer — uses a token\n\n\nSo Bearer simply tells the server which ..."
url: "https://hashnode.com/posts/jwt-description/691185d07ca739e023e4832e"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [JWT Description](https://remember-me-functionality.hashnode.dev/jwt-description?utm_source=hashnode&utm_medium=feed)

Why “Bearer” Exists In the early days, there were several types of authorization schemes, like: Basic — sends username and password encoded in base64 Digest — uses hashed credentials Bearer — uses a token So Bearer simply tells the server which ...

Nov 10, 2025 · 13 min read · remember-me-functionality.hashnode.dev  
Read the article

-   [#jwtauthentication](https://hashnode.com/tag/jwtauthentication)
-   [#jwts](https://hashnode.com/tag/jwts)

## Written by

[Niraj Maharjan](https://hashnode.com/@niraj-maharjan)

@niraj-maharjan

  
[View profile](https://hashnode.com/@niraj-maharjan)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.