diff --git a/apps/docs/content/concepts/structure/projects.mdx b/apps/docs/content/concepts/structure/projects.mdx index b49c18b86..9dec7a35c 100644 --- a/apps/docs/content/concepts/structure/projects.mdx +++ b/apps/docs/content/concepts/structure/projects.mdx @@ -7,7 +7,7 @@ import ProjectDescription from './\_project_description.mdx'; -To learn how to set up a project read this management console guide [here](../../guides/manage/console/projects-overview.mdx). +To learn how to set up a project read this management console guide [here](../../guides/manage/console/projects-overview). ## Applications diff --git a/apps/docs/content/guides/integrate/back-channel-logout.mdx b/apps/docs/content/guides/integrate/back-channel-logout.mdx index 1773877af..a3a20b0f0 100644 --- a/apps/docs/content/guides/integrate/back-channel-logout.mdx +++ b/apps/docs/content/guides/integrate/back-channel-logout.mdx @@ -52,7 +52,7 @@ provides the possibility to match the exact SSO session, which was terminated. ### Client To enable the back-channel logout on an application, they simply need to register a `backchannel_logout_uri` as part of their -configuration, e.g. [creating an OIDC application](https://zitadel.com/docs/reference/api/management/management-service-add-oidc-app). +configuration, e.g. [creating an OIDC application](/guides/manage/console/applications-overview). As soon as the URI is set, every new authorization request will register a back-channel notification to be sent once the session is terminated by a user sign out. diff --git a/apps/docs/content/guides/integrate/login/saml.mdx b/apps/docs/content/guides/integrate/login/saml.mdx index cff97b5d5..a63ffbf68 100644 --- a/apps/docs/content/guides/integrate/login/saml.mdx +++ b/apps/docs/content/guides/integrate/login/saml.mdx @@ -261,9 +261,9 @@ To test SAML scenarios with ZITADEL, follow these steps: - Configure an identity provider that supports SAML. - Set up the necessary metadata and endpoints. Here are some guides to help with this setup: - - [Configure Entra ID as a SAML IdP](https://zitadel.com/docs/guides/integrate/identity-providers/azure-ad-saml) - - [Configure Okta as a SAML IdP](https://zitadel.com/docs/guides/integrate/identity-providers/okta-saml) - - [Configure MockSAML as a SAML IdP](https://zitadel.com/docs/guides/integrate/identity-providers/mocksaml) + - [Configure Entra ID as a SAML IdP](/guides/integrate/identity-providers/azure-ad-saml) + - [Configure Okta as a SAML IdP](/guides/integrate/identity-providers/okta_saml) + - [Configure MockSAML as a SAML IdP](/guides/integrate/identity-providers/mocksaml) 3. Create test users and simulate authentication requests: - Create test users in ZITADEL. diff --git a/apps/docs/content/guides/integrate/service-accounts/authenticate-service-accounts.mdx b/apps/docs/content/guides/integrate/service-accounts/authenticate-service-accounts.mdx index 06e5cf5cb..c0eab4bb9 100644 --- a/apps/docs/content/guides/integrate/service-accounts/authenticate-service-accounts.mdx +++ b/apps/docs/content/guides/integrate/service-accounts/authenticate-service-accounts.mdx @@ -131,6 +131,6 @@ However, [client credentials authentication](./client-credentials) might be cons * [Service Account API reference](/reference/api/user) * [OIDC JWT with private key](/apis/openidoauth/authn-methods#jwt-with-private-key) authentication method reference * [Access ZITADEL APIs](../zitadel-apis/access-zitadel-apis) -* Validate access tokens with [token introspection with private key jwt](../token-introspection/private-key-jwt.mdx) +* [Validate access tokens with token introspection using private key JWT](./private-key-jwt) diff --git a/apps/docs/content/guides/manage/cloud/support.mdx b/apps/docs/content/guides/manage/cloud/support.mdx index 49c77a8d1..7e4053c55 100644 --- a/apps/docs/content/guides/manage/cloud/support.mdx +++ b/apps/docs/content/guides/manage/cloud/support.mdx @@ -9,7 +9,7 @@ We describe our [support services](/legal/service-description/support-services) ## General -We always recommend first having a look at our [documentation](/docs), [discord chat](https://zitadel.com/chat) and [GitHub repository](https://github.com/zitadel/zitadel). You can also ask our AI assistant for help before contacting Support. +We always recommend first having a look at our [documentation](https://zitadel.com/docs), [discord chat](https://zitadel.com/chat) and [GitHub repository](https://github.com/zitadel/zitadel). You can also ask our AI assistant for help before contacting Support. ![](../../../../public/img/manuals/portal/customer_portal_general_support.png) diff --git a/apps/docs/content/guides/manage/customize/restrictions.mdx b/apps/docs/content/guides/manage/customize/restrictions.mdx index 528b84a5f..ec65760a3 100644 --- a/apps/docs/content/guides/manage/customize/restrictions.mdx +++ b/apps/docs/content/guides/manage/customize/restrictions.mdx @@ -2,7 +2,7 @@ title: Feature Restrictions --- -New self-hosted and [ZITADEL Cloud instances](https://zitadel.com/signin) are unrestricted by default. +New self-hosted and [ZITADEL Cloud instances](https://zitadel.com/admin) are unrestricted by default. Self-hosters can change this default using the DefaultInstance.Restrictions configuration section. Users with the role IAM_OWNER can change the restrictions of their instance using the [Feature Restrictions Admin API](/reference/api/admin). Currently, the following restrictions are available: diff --git a/apps/docs/content/guides/start/quickstart.mdx b/apps/docs/content/guides/start/quickstart.mdx index e887a3497..66a0ce7d7 100644 --- a/apps/docs/content/guides/start/quickstart.mdx +++ b/apps/docs/content/guides/start/quickstart.mdx @@ -21,7 +21,7 @@ Set up your ZITADEL account and organization to begin managing identities for yo You first need access to the ZITADEL Cloud Customer Portal. This is the administrative hub for managing your billing, teams, and instances. -1. **Sign Up**: Go to [zitadel.com](http://zitadel.com) and select Sign Up. +1. **Sign Up**: Go to [zitadel.com](https://zitadel.com) and select Sign Up. 2. **Onboarding**: Follow the prompts to verify your email and set up your Portal Team. - Tip: We recommend using Passkeys for a secure, passwordless login experience. 3. **Access**: Once authenticated, you will be redirected to the Customer Portal dashboard. diff --git a/apps/docs/content/legal/policies/brand-trademark-policy.mdx b/apps/docs/content/legal/policies/brand-trademark-policy.mdx index f598b1ee5..1e5abc2ee 100644 --- a/apps/docs/content/legal/policies/brand-trademark-policy.mdx +++ b/apps/docs/content/legal/policies/brand-trademark-policy.mdx @@ -34,7 +34,7 @@ To ensure the logo is used as intended, we provide specific examples below and r - Use in architecture diagrams without implying affiliation or partnership - Editorial and informational purposes such as blog posts or news articles -- Linking back to our [website](https://zitadel.com), official [repositories](https://github.com/zitadel), or [documentation](/docs) +- Linking back to our [website](https://zitadel.com), official [repositories](https://github.com/zitadel), or [documentation](https://zitadel.com/docs) - Indicating that the software is available for use or installation without implying any affiliation or endorsement ### Not acceptable diff --git a/apps/docs/content/legal/policies/privacy-policy.mdx b/apps/docs/content/legal/policies/privacy-policy.mdx index b2ffbf275..4e6756a42 100644 --- a/apps/docs/content/legal/policies/privacy-policy.mdx +++ b/apps/docs/content/legal/policies/privacy-policy.mdx @@ -325,7 +325,7 @@ Our Site is not intended for or directed to children under the age of 14. We do We may revise this privacy policy from time to time and will post the date it was last updated at the top of this privacy policy. We will provide additional notice to you if we make any changes that materially affect your privacy rights. -Please subscribe to updates in our [Trust Center](http://trust.zitadel.com/updates) to receive future notices and updates. +Please subscribe to updates in our [Trust Center](https://trust.zitadel.com/updates) to receive future notices and updates. ## Contact us diff --git a/apps/docs/content/sdk-examples/introduction.mdx b/apps/docs/content/sdk-examples/introduction.mdx index a52e784d5..9f8247d3b 100644 --- a/apps/docs/content/sdk-examples/introduction.mdx +++ b/apps/docs/content/sdk-examples/introduction.mdx @@ -34,7 +34,7 @@ To further streamline your setup, simply visit the management console in Zitadel ![](../../public/img/sdk-examples/console.png) -To begin configuring login for any of these samples, start [here](https://zitadel.com/signin). +To begin configuring login for any of these samples, start [here](/guides/manage/console/console-overview). ## OIDC Libraries diff --git a/apps/docs/content/self-hosting/deploy/troubleshooting/_note_instance_not_found.mdx b/apps/docs/content/self-hosting/deploy/troubleshooting/_note_instance_not_found.mdx index 4d670262c..13590b666 100644 --- a/apps/docs/content/self-hosting/deploy/troubleshooting/_note_instance_not_found.mdx +++ b/apps/docs/content/self-hosting/deploy/troubleshooting/_note_instance_not_found.mdx @@ -1,5 +1,5 @@ This guide is based on a local setup. If you encounter an error "Instance Not Found" please read the following section: -[Instance not found](/self-hosting/deploy/troubleshooting#instance-not-found) +[Instance not found](/self-hosting/deploy/troubleshooting/troubleshooting#instance-not-found) diff --git a/apps/docs/lib/sidebar-data.ts b/apps/docs/lib/sidebar-data.ts index 0e7d51345..32f92fc07 100644 --- a/apps/docs/lib/sidebar-data.ts +++ b/apps/docs/lib/sidebar-data.ts @@ -631,7 +631,7 @@ export const guidesSidebar: readonly SidebarItem[] = [ "guides/integrate/identity-providers/azure-ad-oidc", "guides/integrate/identity-providers/azure-ad-saml", "guides/integrate/identity-providers/okta-oidc", - "guides/integrate/identity-providers/okta-saml", + "guides/integrate/identity-providers/okta_saml", "guides/integrate/identity-providers/keycloak", "guides/integrate/identity-providers/onelogin-saml", "guides/integrate/identity-providers/pingfederate-saml",