Authorization header
The request header that carries a client’s credentials, such as Authorization: Bearer <token> or Authorization: Basic <encoded>.
In more detail
The first word names the scheme. Credentials belong here rather than in the address, and this header must be kept out of logs and forwarded carefully by proxies.
Examples
Authorization: Basic c3ZjLXJlcG9ydDpub3QtYS1yZWFsLXBhc3N3b3JkAuthorization: Bearer <token>Related terms
- bearer token — A token that grants access to whoever presents it, sent as Authorization: Bearer <token>, without any further proof of identity.
- Basic authentication — An HTTP authentication scheme that sends a user name and password in the Authorization header, joined with a colon and Base64-encoded.
- WWW-Authenticate — The response header sent with 401 Unauthorized that tells the client which authentication scheme to use, such as Basic or Bearer.
- secret — Any value that grants access, such as a password, access token or private key, and must be kept out of code and version control.
- HTTP — The protocol web browsers and web servers use to send requests and responses.
- TLS — The encryption that protects data travelling over a network, the S in HTTPS.
Taught in
- Basic Auth, Tokens And Sessions — Modern API Architecture: REST, GraphQL & gRPC
- JSON Web Tokens — Modern API Architecture: REST, GraphQL & gRPC
- Data States: Security at Rest, in Transit, and in Use — Cybersecurity Fundamentals, GRC & Cryptography