andwati/zitadel
1
0
Fork 0
mirror of https://github.com/andwati/zitadel.git synced 2026-10-18 05:52:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: tweaking titles for better SEO appeal (#11852)

Browse Source 
Just updating some title and descriptions for better SEO discovery

---------

Co-authored-by: Copilot Autofix powered by AI <[email protected]>
This commit is contained in:
Florian Forster
2026-03-16 20:03:11 -03:00
committed by GitHub
co-authored by Copilot Autofix powered by AI
parent 34e6a792d2
commit 279f592d80
3 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
apps/docs/content/guides/integrate/login/oidc/login-users.mdx
+5 -5
View File
@@ -1,7 +1,7 @@
---
title: Authenticate users with OpenID Connect
description: "Authenticate users with OpenID Connect using ZITADEL's authorization code flow and Proof Key for Code Exchange (PKCE)"
sidebar_label: OIDC Code Flow + PKCE
title: "OpenID Connect (OIDC) Authentication: Authorization Code Flow & PKCE guide"
description: "Step-by-step guide to authenticating users in your application using OpenID Connect (OIDC). Learn how to implement the Authorization Code flow with PKCE for maximum security."
sidebar_label: OIDC Authorization Code Flow + PKCE
---
import AuthMethods from "./_authmethods.mdx";
@@ -24,7 +24,7 @@ But regardless of the app type we recommend using Proof Key for Code Exchange (P
Please read the following guide about the [different-client-profiles](./oauth-recommended-flows#different-client-profiles) and why to use PKCE.
### Code Flow
### Authorization Code Flow
For a basic understanding of OAuth and its flows, we'll briefly describe the most important flow: **Authorization Code**.
@@ -65,7 +65,7 @@ This will start a wizard asking you for an application name and a type.
#### Authentication method
After selecting WEB, you'll next have to choose an authentication method. As mentioned before we recommend using PKCE.
For even better security you could switch to JWT or just rely on the standard Code Flow. For security reasons we don't
For even better security you could switch to JWT or just rely on the standard Authorization Code Flow. For security reasons we don't
recommend using POST and will not cover it in this guide.
Please change the authentication method here as well, if you did so in the wizard, so we can better guide you through the process:
apps/docs/content/guides/integrate/token-exchange.mdx
+2 -2
View File
@@ -1,6 +1,6 @@
---
title: Impersonation and delegation using Token Exchange
description: "Exchange tokens with different scopes, audiences, or subjects using RFC 8693 OAuth 2.0 Token Exchange grant and ZITADEL"
title: "OAuth 2.0 Token Exchange (RFC 8693): Impersonation & Delegation"
description: "Learn how to implement OAuth 2.0 Token Exchange (RFC 8693) in ZITADEL to securely exchange tokens for different scopes, audiences, or to impersonate users."
sidebar_label: Token Exchange
---
apps/docs/content/self-hosting/manage/configure/configure.mdx
+2 -2
View File
@@ -1,6 +1,6 @@
---
title: Configuration Options in ZITADEL
description: "Detailed guide to configuring ZITADEL using runtime files, database initialization settings, and environment variables."
title: "Self-Hosted ZITADEL Configuration: Runtime Settings & Environment Variables"
description: "Complete guide to configuring your self-hosted ZITADEL environment using the defaults.yaml runtime file, database initialization steps, and environment variables."
sidebar_label: Configuration
---