Difference between revisions of "Bearer token"
Jump to navigation
Jump to search
Tags: Mobile web edit, Mobile edit |
|||
| (21 intermediate revisions by the same user not shown) | |||
| 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]] | + | [[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]] (JWT). |
| + | [[Authorization: Bearer]] 31ada4fd-adec-460c-809a-9e56ceb75269 | ||
| − | + | [[K8s]]: | |
| + | [[curl $APISERVER/api --header]] "Authorization: Bearer $[[TOKEN]]" --insecure | ||
| + | |||
| + | |||
| + | [[curl -H]] | ||
== Related == | == Related == | ||
| + | * [[Access EKS API using a Bearer token]] | ||
| + | * [[curl --header]] | ||
* [[Slack token]] | * [[Slack token]] | ||
| − | * [[PAT]] | + | * [[Personal access token (PAT)]] |
* [[Kubernetes dashboard]] | * [[Kubernetes dashboard]] | ||
| − | * [[HTTP header]]: [[HTTP Header: Authorization|Authorization]] | + | * [[HTTP header]]: <code>[[HTTP Header: Authorization|Authorization:]]</code> |
| + | * [[Kubernetes Authentication]]: [[Kubernetes bearer tokens]] | ||
| + | * <code>[[sts:GetServiceBearerToken]]</code> | ||
| + | * [[AWS bearer tokens]] | ||
| + | * [[TOKEN]] | ||
| + | * [[gcloud auth print-access-token]] | ||
| + | * [[~/Library/Ethereum/geth/jwtsecret]] | ||
== See also == | == See also == | ||
| Line 15: | Line 28: | ||
* {{JSON}} | * {{JSON}} | ||
| − | [[Category: | + | [[Category:Authentication]] |
Latest revision as of 15:25, 8 May 2024
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 (JWT).
Authorization: Bearer 31ada4fd-adec-460c-809a-9e56ceb75269
K8s:
curl $APISERVER/api --header "Authorization: Bearer $TOKEN" --insecure
curl -H
Related[edit]
- Access EKS API using a Bearer token
- curl --header
- Slack token
- Personal access token (PAT)
- Kubernetes dashboard
- HTTP header:
Authorization: - Kubernetes Authentication: Kubernetes bearer tokens
sts:GetServiceBearerToken- AWS bearer tokens
- TOKEN
- gcloud auth print-access-token
- ~/Library/Ethereum/geth/jwtsecret
See also[edit]
- 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:
