andwati/zitadel
1
0
Fork 0
mirror of https://github.com/andwati/zitadel.git synced 2026-10-25 00:32:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(integrate): create automatic overviews, move brokering (#5721)

Browse Source 
* overviews in sidebars

* move identity brokering to features

* fix links
This commit is contained in:
mffap
2023-04-20 17:04:40 +02:00
committed by GitHub
parent e083092605
commit a9d6e92873
6 changed files with 31 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/docs/guides/integrate/identity-providers/introduction.md
-22
View File
@@ -1,22 +0,0 @@
---
title: Identity Brokering
---
## What are Identity Brokering and Federated Identities?
Federated identity management is an arrangement built upon the trust between two or more domains. Users of these domains are allowed to access applications and services using the same identity.
This identity is known as federated identity and the pattern behind this is identity federation.
A service provider that specializes in brokering access control between multiple service providers (also referred to as relying parties) is called an identity broker.
Federated identity management is an arrangement that is made between two or more such identity brokers across organizations.
For example, if Google is configured as an identity provider in your organization, the user will get the option to use his Google Account on the Login Screen of ZITADEL. Because Google is registered as a trusted identity provider, the user will be able to login in with the Google account after the user is linked with an existing ZITADEL account (if he is already registered) or a new one with the claims provided by Google.
![Identity Brokering](/img/guides/identity_brokering.png)
## How to use external identity providers in ZITADEL
Configure external identity providers on the instance level or just for one organization via the [Console](/guides/manage/console/instance-settings#identity-providers) or ZITADEL APIs.
The guides listed in this section will help you set up specific identity providers.
ZITADEL also provides templates to configure generic identity providers, which don't have templates.
docs/docs/guides/manage/console/instance-settings.mdx
+1 -2
View File
@@ -141,8 +141,7 @@ Configure the different lifetimes checks for the login process:
You can configure all kinds of external identity providers for identity brokering, which support OIDC (OpenID Connect).
Create a new identity provider configuration and enable it in the list afterwards.
For a detailed guide about how to configure a new identity provider for identity brokering have a look at our guide:
[Identity Brokering](/guides/integrate/identity-providers/introduction.md)
For a detailed guide about how to configure a new identity provider for identity brokering have a look at our [identity provider guides](/guides/integrate/identity-providers).
## Password Complexity
docs/docs/guides/manage/customize/behavior.md
+1 -1
View File
@@ -11,7 +11,7 @@ Before you start, make sure you have everything set up correctly.
- You need to be at least a ZITADEL _ORG_OWNER_
- Your ZITADEL organization needs to have the actions feature enabled. <!-- TODO: How to enable it for SaaS ZITADEL? -->
- [Your ZITADEL organization needs to have at least one external identity provider enabled](../../integrate/identity-providers/introduction.md)
- [Your ZITADEL organization needs to have at least one external identity provider enabled](../../integrate/identity-providers)
- [You need to have at least one role configured for a project](../console/projects)
## Copy some information for the action
docs/docs/guides/solution-scenarios/configurations.mdx
+1 -1
View File
@@ -15,7 +15,7 @@ If a user of this organization wants to login, you don't want them to enter thei
### Settings
1. Go to the "Identity Providers" Settings of the organization
2. Configure the needed identity provider: Read this [guide](../integrate/identity-providers/introduction.md) if you don't know how
2. Configure the needed identity provider: Read this [guide](../integrate/identity-providers) if you don't know how
3. Go to the "Login Behavior and Security" settings of the organization
4. Disable "Username Password Allowed" and enable "External IDP allowed" in the Advanced Section