andwati/zitadel
1
0
Fork 0
mirror of https://github.com/andwati/zitadel.git synced 2026-11-14 01:45:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore: naming inconsistency application (#11431)

Browse Source
This commit is contained in:
Wim Van Laer
2026-02-04 07:20:07 +00:00
committed by GitHub
parent 04c58c5b3f
commit 61d4060df3
96 changed files with 22550 additions and 22674 deletions
Download Patch File Download Diff File Expand all files Collapse all files
apps/docs/content/concepts/architecture/secrets.mdx
+1 -1
View File
@@ -25,7 +25,7 @@ ZITADEL uses the following principles when handling Secrets across their lifecyc
## Secrets Storage
By default ZITADEL stores secrets from its users, clients as well as its generated secrets like signing keys in the database.
By default ZITADEL stores secrets from its users, applications as well as its generated secrets like signing keys in the database.
To protect the secrets against extraction from database as well as database dumps they are encrypted with AES256.
<Callout>
apps/docs/content/concepts/features/selfservice.mdx
+1 -1
View File
@@ -73,7 +73,7 @@ Read more about [Service Users](/guides/integrate/service-users/authenticate-ser
## Logout
Users can terminate the session for all their users (logout).
A client can also implement this by calling the [specific endpoint](/apis/openidoauth/endpoints#end-session-endpoint).
An application can also implement this by calling the [specific endpoint](/apis/openidoauth/endpoints#end-session-endpoint).
## Profile
apps/docs/content/concepts/structure/_org_description.mdx
+1 -1
View File
@@ -8,7 +8,7 @@ ZITADEL is organized around the idea that:
Organizations in ZITADEL are therefore comparable to tenants of a system or organizational units of a directory based system.
You can use projects within your organization to manage the security context of closely related components, such as roles, grants and authorizations for multiple clients. You can set up multiple projects within your organization.
You can use projects within your organization to manage the security context of closely related components, such as roles, grants and authorizations for multiple applications. You can set up multiple projects within your organization.
ZITADEL allows you to give other organizations permission to manage certain aspects of a project within your organization on their own. This means you could set up a project with roles that should exist within your service/software, but allow another organization to allocate the roles to users within their own organization. As a service provider, you will find this feature useful, as it allows you to establish a self-service culture for your business customers.
apps/docs/content/concepts/structure/applications.mdx
+2 -2
View File
@@ -6,12 +6,12 @@ sidebar_label: Applications
import AppType from "../../guides/manage/console/_application-types.mdx";
Applications are the entry point to your project.
[Users](./users) either login into one of your clients and interact with them directly or use one of your APIs.
[Users](./users) either login into one of your applications and interact with them directly or use one of your APIs.
All applications share the roles and authorizations of their [project](./projects).
## Supported application types
ZITADEL supports the following client types:
ZITADEL supports the following application types:
<AppType components={props.components} />