TheArchive/zitadel
1
0
Fork 0
mirror of https://github.com/zitadel/zitadel.git synced 2025-08-12 07:47:32 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: update introduction.md (#5408)

Browse Source 
* Update introduction.md

* Update docs/docs/guides/integrate/identity-providers/introduction.md

Co-authored-by: mffap <mpa@zitadel.com>

---------

Co-authored-by: mffap <mpa@zitadel.com>
This commit is contained in:
Dakshitha Ratnayake
2023-03-09 18:22:04 +05:30
committed by GitHub
parent 26fdc3e84e
commit 5c8caf882b
1 changed files with 8 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
docs/docs/guides/integrate/identity-providers/introduction.md
View File

@@ -2,23 +2,21 @@
title: Identity Brokering
---
## What is Identity Brokering and Federated Identities?
## 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 as identity federation.
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 identity broker.
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.
Example:
If Google is configured as identity provider on your organization, the user will get the option to use his Google Account on the Login Screen of ZITADEL (1).
ZITADEL will redirect the user to the login screen of Google where he as to authenticated himself (2) and is sent back after he has finished that (3).
Because Google is registered as trusted identity provider the user will be able to login in with the Google account after he linked an existing ZITADEL Account or just registered a new one with the claims provided by Google (4)(5).
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 instance level or just for one organization via [Console](/guides/manage/console/instance-settings#identity-providers) or APIs.
The guides in this will help you to set up specific identity providers.
ZITADEL provides also templates to configure generic identity providers, which don't have a template.
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.