mirror of
https://github.com/zitadel/zitadel.git
synced 2025-12-05 08:52:05 +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:
@@ -15,7 +15,7 @@ The [OpenID Connect & OAuth endpoints](/docs/apis/openidoauth/endpoints) and [SA
|
||||
## Authentication & authorization
|
||||
|
||||
ZITADEL implements industry standards such as OpenID Connect, OAuth 2.0, or SAML for authentication.
|
||||
Please refer to our guides how to [authenticate users](/docs/guides/integrate/human-users) through an interactive authentication process and how to [authenticate service users](/docs/guides/integrate/serviceusers) with a programmatic authentication.
|
||||
Please refer to our guides how to [authenticate users](/docs/guides/integrate/login/login-users) through an interactive authentication process and how to [authenticate service users](/docs/guides/integrate/serviceusers) with a programmatic authentication.
|
||||
|
||||
### OpenID Connect & OAuth
|
||||
|
||||
|
||||
@@ -57,7 +57,7 @@ Depending on the authentication and authorization flow of your application you m
|
||||
for most application types. The playground appends automatically a code challenge
|
||||
for PKCE flows.
|
||||
|
||||
You need to append a "Code Challenge" by providing a random <span className="text-teal-600">Code Verifier</span> that is being hashed and encoded in the request to the token endpoint, please see our [guide](/guides/integrate/login-users#token-request) for more details.
|
||||
You need to append a "Code Challenge" by providing a random <span className="text-teal-600">Code Verifier</span> that is being hashed and encoded in the request to the token endpoint, please see our [guide](/guides/integrate/login/oidc/login-users#token-request) for more details.
|
||||
|
||||
More in the [documentation](/apis/openidoauth/authn-methods) about authentication methods.
|
||||
|
||||
@@ -123,6 +123,6 @@ This can be achieved by adding the scope `urn:zitadel:iam:org:project:id:zitadel
|
||||
|
||||
## How to use ZITADEL in your project
|
||||
|
||||
Please refer to our [guide](/guides/integrate/login-users) on how to login users.
|
||||
Please refer to our [guide](/guides/integrate/login/oidc/login-users) on how to login users.
|
||||
|
||||
OpenID Connect certified libraries should allow you to customize the parameters and define scopes for the authorization request. You can also continue by using one of our [example applications](/docs/sdk-examples/introduction).
|
||||
|
||||
Reference in New Issue
Block a user