Difference between revisions of "Bearer token"
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 5: | Line 5: | ||
[[K8s]]: | [[K8s]]: | ||
[[curl $APISERVER/api --header]] "Authorization: Bearer $[[TOKEN]]" --insecure | [[curl $APISERVER/api --header]] "Authorization: Bearer $[[TOKEN]]" --insecure | ||
| + | |||
| + | |||
| + | [[curl -H]] | ||
== Related == | == Related == | ||
| Line 18: | Line 21: | ||
* [[TOKEN]] | * [[TOKEN]] | ||
* [[gcloud auth print-access-token]] | * [[gcloud auth print-access-token]] | ||
| + | * [[~/Library/Ethereum/geth/jwtsecret]] | ||
== See also == | == See also == | ||
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:
