mirror of
https://github.com/zitadel/zitadel.git
synced 2025-12-10 07:12:41 +00:00
docs: move jwt idp to guides (#7570)
This commit is contained in:
@@ -2,7 +2,7 @@
|
||||
title: External Authentication Flow
|
||||
---
|
||||
|
||||
This flow is executed if the user logs in using an [identity provider](/guides/integrate/identity-providers) or using a [jwt token](/concepts/structure/jwt_idp).
|
||||
This flow is executed if the user logs in using an [identity provider](/guides/integrate/identity-providers) or using a [jwt token](/guides/integrate/identity-providers/jwt-idp).
|
||||
|
||||
The flow is represented by the following Ids in the API: `FLOW_TYPE_EXTERNAL_AUTHENTICATION` and `1`
|
||||
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: JWT IDP
|
||||
---
|
||||
|
||||
|
||||
# JWT IDP
|
||||
|
||||
JSON Web Token Identity Provider (JWT IDP) gives you the possibility to use an (existing) JWT as federated identity.
|
||||
@@ -17,7 +16,7 @@ All you need to provide is an endpoint where ZITADEL can receive a JWT and some
|
||||
|
||||
The authentication process then might look like the following:
|
||||
|
||||

|
||||

|
||||
|
||||
1. The user is logged into the existing application and the WAF holds the session information. It might even send a JWT to the application.
|
||||
The new application is opened by clicking on a link in the existing application.
|
||||
Reference in New Issue
Block a user