Difference between revisions of "Kubernetes bearer tokens"
Jump to navigation
Jump to search
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
* https://kubernetes.io/docs/reference/access-authn-authz/authentication/#authentication-strategies | * https://kubernetes.io/docs/reference/access-authn-authz/authentication/#authentication-strategies | ||
| + | * https://kubernetes.io/docs/reference/access-authn-authz/authentication/#putting-a-bearer-token-in-a-request | ||
| + | Putting a Bearer Token in a Request | ||
| + | When using bearer token authentication from an http client, the API server expects an Authorization header with a value of Bearer <token>. The bearer token must be a character sequence that can be put in an HTTP header value using no more than the encoding and quoting facilities of HTTP. For example: if the bearer token is 31ada4fd-adec-460c-809a-9e56ceb75269 then it would appear in an HTTP header as shown below. | ||
| + | |||
| + | Authorization: Bearer 31ada4fd-adec-460c-809a-9e56ceb75269 | ||
| + | |||
| + | |||
| + | |||
| + | == Activities == | ||
| + | * [[Access Kubernetes REST API using default token]] | ||
== Related == | == Related == | ||
| − | * [[ | + | * [[Service accounts]] |
| + | [[kubectl create token]] | ||
== See also == | == See also == | ||
* {{Kubernetes Authentication}} | * {{Kubernetes Authentication}} | ||
| + | |||
| + | [[Category:K8s]] | ||
Latest revision as of 16:58, 31 October 2023
- https://kubernetes.io/docs/reference/access-authn-authz/authentication/#authentication-strategies
- https://kubernetes.io/docs/reference/access-authn-authz/authentication/#putting-a-bearer-token-in-a-request
Putting a Bearer Token in a Request When using bearer token authentication from an http client, the API server expects an Authorization header with a value of Bearer <token>. The bearer token must be a character sequence that can be put in an HTTP header value using no more than the encoding and quoting facilities of HTTP. For example: if the bearer token is 31ada4fd-adec-460c-809a-9e56ceb75269 then it would appear in an HTTP header as shown below.
Authorization: Bearer 31ada4fd-adec-460c-809a-9e56ceb75269
Activities[edit]
Related[edit]
kubectl create token
See also[edit]
Advertising:
