Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Identity for cluster clients in 8.7 Clusters #4803

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
+4 −0
Draft

Identity for cluster clients in 8.7 Clusters #4803

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/components/console/manage-clusters/manage-api-clients.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,10 @@ When the rate limit is triggered, the client will receive an HTTP 429 response.

## Create a client

:::caution
In **8.7** Clusters, the Client Scopes will be managed through the cluster Identity component. The only scope that is still managed in Console is the Cluster **Secrets** scope. To learn more about managing Clients in **8.7** Clusters please refer to the [Identity](/components/identity/manage-api-clients.md) Documentation.
:::

Currently, Camunda 8 SaaS supports the following scopes:

- Zeebe - Access to the [Zeebe gRPC](/apis-tools/zeebe-api/grpc.md) and [REST](/apis-tools/camunda-api-rest/camunda-api-rest-overview.md) APIs.
Expand Down
Loading