docs: fix broken docs links and insecure redirects (#11591)

Summary
- audited doc CSVs to replace insecure http links and ensure paths point
to the migrated `apps/docs` structure
- preserved downstream link intent while keeping references aligned with
the `/docs` deployment prefix

---------

Co-authored-by: Copilot <[email protected]>
This commit is contained in:
Florian Forster
2026-02-13 11:01:11 -08:00
committed by GitHub
co-authored by Copilot
parent ca6bd9d6a2
commit 943d9e0967
12 changed files with 14 additions and 14 deletions
@@ -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.
@@ -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.
@@ -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)
<DocCardList />