docs: add available_from for vmauth\jwt feature

Follow-up on
https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10499
This commit is contained in:
Max Kotliar
2026-02-25 15:24:39 +02:00
parent 8f4eca39f7
commit 8f34284dd2

View File

@@ -250,7 +250,7 @@ See also [authorization](#authorization), [routing](#routing) and [load balancin
### JWT Token auth proxy
`vmauth` can authorize access to backends depending on the provided [JWT token](https://www.jwt.io/) in `Authorization` request header.
`vmauth` can authorize access{{% available_from "#" %}} to backends depending on the provided [JWT token](https://www.jwt.io/) in `Authorization` request header.
JWT tokens are verified using RSA or ECDSA public keys. The following auth config proxies requests to [single-node VictoriaMetrics](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) if they contain a valid JWT token:
```yaml
@@ -298,7 +298,7 @@ JWT authentication cannot be combined with other auth methods (`bearer_token`, `
#### JWT claim-based request templating
`vmauth` can dynamically rewrite upstream URLs and request headers using values from the JWT `vm_access` claim.
`vmauth` can dynamically rewrite{{% available_from "#" %}} upstream URLs and request headers using values from the JWT `vm_access` claim.
This enables routing different users to different backends or tenants based solely on the JWT token,
without maintaining separate user configs per tenant.