docs(concepts): Update resources and features, add account linking (#7934)

* account linking

* updates to concepts and features

* Apply suggestions from code review

* Apply suggestions from code review

Co-authored-by: Fabi <[email protected]>

---------

Co-authored-by: Fabi <[email protected]>
This commit is contained in:
mffap
2024-05-13 08:29:25 +02:00
committed by GitHub
co-authored by Fabi
parent 3396657c3f
commit 6942324741
9 changed files with 134 additions and 36 deletions
@@ -0,0 +1,5 @@
- [**Web**](#web) (Server-side web applications such as java, .net, ...)
- [**Native**](#native) (native, mobile or desktop applications)
- [**User Agent**](#user-agent) (single page applications / SPA, generally JavaScript executed in the browser)
- [**API**](#api) (OAuth Resource Server)
- [**SAML**](#saml)
@@ -7,6 +7,7 @@ import ThemedImage from "@theme/ThemedImage";
import AuthType from "../../integrate/application/_auth-type.mdx";
import ReviewConfig from "../../integrate/application/_review-config.mdx";
import AppType from "./_application-types.mdx";
## What is an application?
@@ -36,13 +37,9 @@ To add an application to your project, click on the add button and select your a
## Application Types
At the moment ZITADEL offers four client types:
At the moment ZITADEL offers five client types:
- [**Web**](#web) (Server-side web applications such as java, .net, ...)
- [**Native**](#native) (native, mobile or desktop applications)
- [**User Agent**](#user-agent) (single page applications / SPA, generally JavaScript executed in the browser)
- [**API**](#api) (OAuth Resource Server)
- [**SAML**](#saml)
<AppType />
The first three options (Web, Native and User Agent) require user interaction, the fourth option (API) has no direct user-interaction.
Depending on the app type, there are small differences in the possible settings.