docs: move jwt idp to guides (#7570)

This commit is contained in:
Silvan
2024-03-20 10:46:05 +01:00
committed by GitHub
parent cc26eb1116
commit b338171585
5 changed files with 6 additions and 4 deletions

View File

@@ -2,7 +2,7 @@
title: External Authentication Flow 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` The flow is represented by the following Ids in the API: `FLOW_TYPE_EXTERNAL_AUTHENTICATION` and `1`

View File

@@ -2,7 +2,6 @@
title: JWT IDP title: JWT IDP
--- ---
# JWT IDP # JWT IDP
JSON Web Token Identity Provider (JWT IDP) gives you the possibility to use an (existing) JWT as federated identity. 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: The authentication process then might look like the following:
![JWT IDP Architecture](/img/concepts/objects/jwt_idp.png) ![JWT IDP Architecture](/img/guides/jwt_idp.png)
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. 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. The new application is opened by clicking on a link in the existing application.

View File

@@ -356,6 +356,7 @@ module.exports = {
"guides/integrate/identity-providers/okta-saml", "guides/integrate/identity-providers/okta-saml",
"guides/integrate/identity-providers/keycloak", "guides/integrate/identity-providers/keycloak",
"guides/integrate/identity-providers/mocksaml", "guides/integrate/identity-providers/mocksaml",
"guides/integrate/identity-providers/jwt-idp",
"guides/integrate/identity-providers/additional-information", "guides/integrate/identity-providers/additional-information",
], ],
}, },

View File

Before

Width:  |  Height:  |  Size: 269 KiB

After

Width:  |  Height:  |  Size: 269 KiB

View File

@@ -27,6 +27,8 @@
{ "source": "/docs/guides/integrate/logout", "destination": "/docs/guides/integrate/login/oidc/logout", "permanent": true }, { "source": "/docs/guides/integrate/logout", "destination": "/docs/guides/integrate/login/oidc/logout", "permanent": true },
{ "source": "/docs/guides/solution-scenarios/onboarding", "destination": "/docs/guides/integrate/onboarding", "permanent": true }, { "source": "/docs/guides/solution-scenarios/onboarding", "destination": "/docs/guides/integrate/onboarding", "permanent": true },
{ "source": "/docs/guides/solution-scenarios/onboarding/b2b", "destination": "/docs/guides/integrate/onboarding/b2b", "permanent": true }, { "source": "/docs/guides/solution-scenarios/onboarding/b2b", "destination": "/docs/guides/integrate/onboarding/b2b", "permanent": true },
{ "source": "/docs/guides/solution-scenarios/onboarding/end-users", "destination": "/docs/guides/integrate/onboarding/end-users", "permanent": true } { "source": "/docs/guides/solution-scenarios/onboarding/end-users", "destination": "/docs/guides/integrate/onboarding/end-users", "permanent": true },
{ "source": "/docs/concepts/structure/jwt_idp", "destination": "/docs/guides/integrate/identity-providers/jwt-idp", "permanent": true },
{ "source": "/docs/concepts/structure/jwt-idp", "destination": "/docs/guides/integrate/identity-providers/jwt-idp", "permanent": true }
] ]
} }