TheArchive/zitadel
1
0
Fork 0
mirror of https://github.com/zitadel/zitadel.git synced 2025-02-28 20:37:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Mark beta features (#9337)

Browse Source 
# Which Problems Are Solved

Currently it is not always obvious if a feature is in beta state, also I
don't know where I can add my feedback if I test the feature.

# How the Problems Are Solved

- Mark beta features with [beta] in sidenav
- Add note on feature description where to add feedback
This commit is contained in:
Fabienne Bühler 2025-02-11 18:55:03 +01:00 committed by GitHub
parent 824228736c
commit 6ef0fcb4d6
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 9 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/docs/guides/integrate/login/oidc/webkeys.md
View File

@ -1,6 +1,6 @@
---
title: OpenID Connect and Oauth2 web keys
sidebar_label: Web keys
sidebar_label: Web keys [Beta]
---
Web Keys in ZITADEL are used to sign and verify JSON Web Tokens (JWT).
@ -22,6 +22,8 @@ endpoints are called with a JWT access token.
:::info
Web keys are an [experimental](/docs/support/software-release-cycles-support#beta) feature. Be sure to enable the `web_key` [feature](/docs/apis/resources/feature_service_v2/feature-service-set-instance-features) before using it.
Test the feature and add improvement or bug reports directly to the [github repository](https://github.com/zitadel/zitadel) or let us know your general feedback in the [discord thread](https://discord.com/channels/927474939156643850/1329100936127320175/threads/1332344892629717075)!
:::
### JSON Web Key

4
docs/docs/guides/integrate/token-exchange.mdx
View File

@ -1,6 +1,6 @@
---
title: Impersonation and delegation using Token Exchange
sidebar_label: Token Exchange
sidebar_label: Token Exchange [Beta]
---
import TokenExchangeTypes from "../../apis/openidoauth/_token_exchange_types.mdx";
@ -11,6 +11,8 @@ The Token Exchange grant implements [RFC 8693, OAuth 2.0 Token Exchange](https:/
:::info
Token Exchange is currently an [experimental beta](/docs/support/software-release-cycles-support#beta) feature. Be sure to enable it on the [feature API](#feature-api) before using it.
Test the feature and add improvement or bug reports directly to the [github repository](https://github.com/zitadel/zitadel) or let us know your general feedback in the [discord thread](https://discord.com/channels/927474939156643850/1333448892083208262)!
:::
In this guide we assume that the application performing the token exchange is already in possession of tokens. You should already have a good understanding on the following topics before starting with this guide:

4
docs/docs/self-hosting/manage/cache.md
View File

@ -1,12 +1,14 @@
---
title: Caches
sidebar_label: Caches
sidebar_label: Caches [Beta]
---
ZITADEL supports the use of a caches to speed up the lookup of frequently needed objects. As opposed to HTTP caches which might reside between ZITADEL and end-user applications, the cache build into ZITADEL uses active invalidation when an object gets updated. Another difference is that HTTP caches only cache the result of a complete request and the built-in cache stores objects needed for the internal business logic. For example, each request made to ZITADEL needs to retrieve and set [instance](/docs/concepts/structure/instance) information in middleware.
:::info
Caches is currently an [experimental beta](/docs/support/software-release-cycles-support#beta) feature.
Test the feature and add improvement or bug reports directly to the [github repository](https://github.com/zitadel/zitadel) or let us know your general feedback in the [discord thread](https://discord.com/channels/927474939156643850/1332343909900222506)!
:::
## Configuration