Difference between revisions of "Bearer token"
Jump to navigation
Jump to search
Tags: Mobile web edit, Mobile edit |
|||
| Line 1: | Line 1: | ||
[[wikipedia:Bearer token]] is an opaque string, not intended to have any meaning to clients using it. Some servers will issue tokens that are a short string of hexadecimal characters, while others may use structured tokens such as [[JSON]] Web Tokens. | [[wikipedia:Bearer token]] is an opaque string, not intended to have any meaning to clients using it. Some servers will issue tokens that are a short string of hexadecimal characters, while others may use structured tokens such as [[JSON]] Web Tokens. | ||
| + | |||
| + | [[Authorization:]] [[Bearer]] 31ada4fd-adec-460c-809a-9e56ceb75269 | ||
== Related == | == Related == | ||
Revision as of 17:24, 13 June 2022
wikipedia:Bearer token is an opaque string, not intended to have any meaning to clients using it. Some servers will issue tokens that are a short string of hexadecimal characters, while others may use structured tokens such as JSON Web Tokens.
Authorization: Bearer 31ada4fd-adec-460c-809a-9e56ceb75269
Related
See also
- OAuth, Bearer Token, Scope, Google for authentication, PKCE, oAuth authorization flow,
express-oauth-server - JWT,
openssl rand, Bearer token, HMAC,JWT_SECRET_KEY, JWT signatures, HS256, RS256 - JSON,
jq, jid, mlr, JWT, BSON, Miller, Content-type:,application/json,BadJSON, Webhook, jsonc, ndjson,import json, Google Custom Search JSON API,jsonpath, JSON-LD, JSON tree, JSON-RPC
Advertising:
