mirror of
https://github.com/zitadel/zitadel.git
synced 2025-08-11 20:27:32 +00:00
docs(integrate): Update login users docs (#7414)
* wip * update intro of device auth * add custom domain concept * wip sidebar * wip introduction * add passkeys * replace azure ad with entra id * wip * wip * login methods * expand sections automatically * update selfservice docs * wip - hosted done * move onboarding * clean up * wip * unbreak my hrefs * finish login users * update managers * add console as feature * update b2b with multi-tenancy * update saml * update console concept * add opaque tokens as knowledge * redirects * intro b2b * remove login/saml * unbreak link * Apply suggestions from code review Co-authored-by: Fabi <fabienne@zitadel.com> * passkeys: add custom domain first * update passkeys * Apply suggestions from code review Co-authored-by: Florian Forster <florian@zitadel.com> * Update docs/docs/guides/integrate/login/login-users.mdx Co-authored-by: Florian Forster <florian@zitadel.com> --------- Co-authored-by: Fabi <fabienne@zitadel.com> Co-authored-by: Florian Forster <florian@zitadel.com>
This commit is contained in:
mffap
105
docs/sidebars.js
105
docs/sidebars.js
@@ -5,6 +5,7 @@ module.exports = {
|
||||
type: "category",
|
||||
label: "Get Started",
|
||||
collapsed: false,
|
||||
link: { type: "doc", id: "guides/start/quickstart" },
|
||||
items: [
|
||||
"guides/start/quickstart",
|
||||
{
|
||||
@@ -50,6 +51,7 @@ module.exports = {
|
||||
{
|
||||
type: "category",
|
||||
label: "Examples & SDKs",
|
||||
link: {type: 'doc', id: 'sdk-examples/introduction'},
|
||||
items: [
|
||||
"sdk-examples/introduction",
|
||||
"sdk-examples/angular",
|
||||
@@ -126,6 +128,10 @@ module.exports = {
|
||||
{
|
||||
type: "category",
|
||||
label: "Console",
|
||||
link: {
|
||||
type: "doc",
|
||||
id: "guides/manage/console/overview",
|
||||
},
|
||||
items: [
|
||||
"guides/manage/console/overview",
|
||||
"guides/manage/console/instance-settings",
|
||||
@@ -195,18 +201,68 @@ module.exports = {
|
||||
items: [
|
||||
{
|
||||
type: "category",
|
||||
label: "Authenticate Users",
|
||||
collapsed: true,
|
||||
label: "Login Users",
|
||||
link: {
|
||||
type: "generated-index",
|
||||
title: "Authenticate Human Users",
|
||||
slug: "guides/integrate/human-users",
|
||||
description: "How to authenticate human users with OpenID Connect",
|
||||
title: "Integrate",
|
||||
slug: "guides/integrate/login",
|
||||
description:
|
||||
"Integrate your users and application with ZITADEL. In this section you will find resource on how to authenticate your users, configure external identity providers, access the ZITADEL APIs to manage resources, and integrate with third party services and tools.",
|
||||
},
|
||||
items: [
|
||||
"guides/integrate/login-users",
|
||||
"guides/integrate/oauth-recommended-flows",
|
||||
"guides/integrate/logout",
|
||||
'guides/integrate/login/login-users',
|
||||
{
|
||||
type: "category",
|
||||
label: "Openid Connect",
|
||||
collapsed: true,
|
||||
link: {
|
||||
type: "generated-index",
|
||||
title: "Authenticate users with OpenID Connect (OIDC)",
|
||||
slug: "guides/integrate/login/oidc",
|
||||
description: "This guide explains how to utilize ZITADEL for user authentication within your applications using OpenID Connect (OIDC). Here, we offer comprehensive guidance on seamlessly integrating ZITADEL's authentication features, ensuring both security and user experience excellence. Throughout this documentation, we'll cover the setup process for ZITADEL authentication, including the recommended OIDC flows tailored to different application types. Additionally, we'll provide clear instructions on securely signing out or logging out users from your application, ensuring data security and user privacy. With our guidance, you'll be equipped to leverage ZITADEL's authentication capabilities effectively, enhancing your application's security posture while delivering a seamless login experience for your users.",
|
||||
},
|
||||
items: [
|
||||
"guides/integrate/login/oidc/login-users",
|
||||
"guides/integrate/login/oidc/oauth-recommended-flows",
|
||||
"guides/integrate/login/oidc/device-authorization",
|
||||
"guides/integrate/login/oidc/logout",
|
||||
],
|
||||
},
|
||||
/*
|
||||
{
|
||||
type: "category",
|
||||
label: "SAML",
|
||||
collapsed: true,
|
||||
link: {
|
||||
type: "generated-index",
|
||||
title: "Authenticate users with openid connect (OIDC)",
|
||||
slug: "guides/integrate/login/saml",
|
||||
description: ".",
|
||||
},
|
||||
items: [
|
||||
{
|
||||
type: "autogenerated",
|
||||
dirName: "guides/integrate/login/saml",
|
||||
},
|
||||
],
|
||||
},*/
|
||||
],
|
||||
},
|
||||
{
|
||||
type: "category",
|
||||
label: "Onboard Customers and Users",
|
||||
link: {
|
||||
type: "generated-index",
|
||||
title: "Onboard Customers and Users",
|
||||
slug: "/guides/integrate/onboarding",
|
||||
description:
|
||||
"When building your own application, one of the first questions you have to face, is 'How do my customers onboard to my application?'\n" +
|
||||
"These guides will explain the built-in solution for onboarding new tenants, customers, and users and how you can handle more advanced onboarding use cases. ",
|
||||
},
|
||||
collapsed: true,
|
||||
items: [
|
||||
"guides/integrate/onboarding/b2b",
|
||||
"guides/integrate/onboarding/end-users",
|
||||
],
|
||||
},
|
||||
{
|
||||
@@ -216,7 +272,7 @@ module.exports = {
|
||||
type: "generated-index",
|
||||
title: "Token Introspection",
|
||||
slug: "/guides/integrate/token-introspection",
|
||||
description:
|
||||
description:
|
||||
"Token introspection is the process of checking whether an access token is valid and can be used to access protected resources. You have an API that acts as an OAuth resource server and can be accessed by user-facing applications. To validate an access token by calling the ZITADEL introspection API, you can use the JSON Web Token (JWT) Profile (recommended) or Basic Authentication for token introspection. It's crucial to understand that the API is entirely separate from the front end. The API shouldn’t concern itself with the token type received. Instead, it's about how the API chooses to call the introspection endpoint, either through JWT Profile or Basic Authentication. Many APIs assume they might receive a JWT and attempt to verify it based on signature or expiration. However, with ZITADEL, you can send either a JWT or an opaque Bearer token from the client end to the API. This flexibility is one of ZITADEL's standout features.",
|
||||
},
|
||||
collapsed: true,
|
||||
@@ -416,25 +472,7 @@ module.exports = {
|
||||
"guides/solution-scenarios/domain-discovery",
|
||||
"guides/solution-scenarios/configurations",
|
||||
"guides/solution-scenarios/frontend-calling-backend-API",
|
||||
"guides/solution-scenarios/device-authorization",
|
||||
"guides/solution-scenarios/restrict-console",
|
||||
{
|
||||
type: "category",
|
||||
label: "Onboarding Customers and Users",
|
||||
link: {
|
||||
type: "generated-index",
|
||||
title: "Onboarding Customers and Users",
|
||||
slug: "/guides/solution-scenarios/onboarding",
|
||||
description:
|
||||
"When building your own application, one of the first questions you have to face, is 'How do my customers onboard to my application?'\n" +
|
||||
"This guide will show you the built-in solution you have, within ZITADEL and how you can use ZITADEL when you have more advanced needs.",
|
||||
},
|
||||
collapsed: true,
|
||||
items: [
|
||||
"guides/solution-scenarios/onboarding/b2b",
|
||||
"guides/solution-scenarios/onboarding/end-users",
|
||||
],
|
||||
}
|
||||
],
|
||||
},
|
||||
{
|
||||
@@ -457,11 +495,14 @@ module.exports = {
|
||||
"concepts/structure/users",
|
||||
"concepts/structure/managers",
|
||||
"concepts/structure/policies",
|
||||
"concepts/features/identity-brokering",
|
||||
"concepts/structure/jwt_idp",
|
||||
"concepts/features/actions",
|
||||
"concepts/features/audit-trail",
|
||||
"concepts/features/selfservice",
|
||||
{
|
||||
type: "autogenerated",
|
||||
dirName: "concepts/features",
|
||||
},
|
||||
{
|
||||
type: "autogenerated",
|
||||
dirName: "concepts/knowledge",
|
||||
},
|
||||
],
|
||||
},
|
||||
{
|
||||
|
||||
Reference in New Issue
Block a user