mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-27 21:50:21 +00:00
Remove unsupported front matter fields
This commit is contained in:
@@ -1,6 +1,5 @@
|
||||
---
|
||||
title: API Keys
|
||||
weight: 7005
|
||||
---
|
||||
|
||||
## API Keys and User Authentication
|
||||
@@ -33,7 +32,7 @@ Users may opt to enable [token hashing](../about-the-api/api-tokens.md).
|
||||
The API key won't be valid after expiration. Shorter expiration periods are more secure.
|
||||
|
||||
Expiration period will be bound by `v3/settings/auth-token-max-ttl-minutes`. If it exceeds the max-ttl, API key will be created with max-ttl as the expiration period.
|
||||
|
||||
|
||||
A scope will limit the API key so that it will only work against the Kubernetes API of the specified cluster. If the cluster is configured with an Authorized Cluster Endpoint, you will be able to use a scoped token directly against the cluster's API without proxying through the Rancher server. See [Authorized Cluster Endpoints](../../pages-for-subheaders/rancher-manager-architecture.md#4-authorized-cluster-endpoint) for more information.
|
||||
|
||||
4. Click **Create**.
|
||||
|
||||
Reference in New Issue
Block a user