auth0 · gabrielraeder · Nov 11, 2025 · Nov 11, 2025 · Nov 13, 2025
diff --git a/main/docs/authenticate/database-connections/password-change.mdx b/main/docs/authenticate/database-connections/password-change.mdx
@@ -10,6 +10,8 @@ title: Change Users' Passwords
   your Auth0 applications.
 'twitter:title': Change Users' Passwords
 ---
+import {AuthLink} from "/snippets/AuthLink.jsx";
+
 import {AuthCodeBlock} from "/snippets/AuthCodeBlock.jsx";
 
 import {AuthCodeGroup} from "/snippets/AuthCodeGroup.jsx";
@@ -57,7 +59,7 @@ If your application uses an interactive password reset flow through the Authenti
 
 If you call the API from the browser, be sure the origin URL is allowed:
 
-Go to [Auth0 Dashboard > Applications > Applications](https://manage.auth0.com/#/applications/{yourClientId}/settings), and add the URL to the **Allowed Origins (CORS)** list.
+Go to <AuthLink href="https://manage.auth0.com/#/applications/{yourClientId}/settings">Auth0 Dashboard > Applications > Applications</AuthLink>, and add the URL to the **Allowed Origins (CORS)** list.
 
 If your connection is a custom database, check to see if the user exists in the database before you invoke the Authentication API for `changePassword`.
 

diff --git a/...authenticate/identity-providers/enterprise-identity-providers/ping-federate.mdx b/...authenticate/identity-providers/enterprise-identity-providers/ping-federate.mdx
@@ -10,6 +10,8 @@ title: Connect Your PingFederate Server to Auth0
   Server and Auth0.
 'twitter:title': Connect Your PingFederate Server to Auth0
 ---
+import {AuthLink} from "/snippets/AuthLink.jsx";
+
 Auth0 lets you create [PingFederate Server](https://documentation.pingidentity.com/pingfederate/pf84/#gettingStartedGuide/concept/gettingStarted.html) connections.
 
 ## Prerequisites
@@ -81,7 +83,7 @@ If additional setup is required for your server (such as attribute mapping), the
 </tr>
 <tr>
 <td><strong>Sign Request</strong></td>
-<td>When enabled, the SAML authentication request will be signed. (Be sure to download and provide the PingFederate server with your <a href="https://{yourDomain}/pem">tenant's certificate</a>.)</td>
+<td>When enabled, the SAML authentication request will be signed. (Be sure to download and provide the PingFederate server with your <AuthLink href="https://{yourDomain}/pem">tenant's certificate</AuthLink>.)</td>
 </tr>
 <tr>
 <td><strong>Sign Request Algorithm</strong></td>

diff --git a/main/docs/authenticate/login/redirect-users-after-login.mdx b/main/docs/authenticate/login/redirect-users-after-login.mdx
@@ -10,11 +10,13 @@ title: Redirect Users
   added to the AllowList.
 'twitter:title': Redirect Users
 ---
+import {AuthLink} from "/snippets/AuthLink.jsx";
+
 You can return users to specific pages (URLs) within your application after validating their <Tooltip tip="ID Token: Credential meant for the client itself, rather than for accessing a resource." cta="View Glossary" href="/docs/glossary?term=ID+Tokens">ID Tokens</Tooltip> (authentication). To see an example of how this works, try the [React: Login Quickstart](/docs/quickstart/spa/react).
 
 ## Redirect users to callback URLs on the AllowList
 
-Because callback URLs can be manipulated by unauthorized parties, Auth0 recognizes only URLs on the AllowList set in the **Allowed Callback URLs** field of an [Application's Settings](https://manage.auth0.com/#/applications/{yourClientId}/settings) as valid. To return users to callback URLs on the AllowList, it is necessary for your application to know how to continue the user on their journey.
+Because callback URLs can be manipulated by unauthorized parties, Auth0 recognizes only URLs on the AllowList set in the **Allowed Callback URLs** field of an <AuthLink href="https://manage.auth0.com/#/applications/{yourClientId}/settings">Application's Settings</AuthLink> as valid. To return users to callback URLs on the AllowList, it is necessary for your application to know how to continue the user on their journey.
 
 There are two methods for doing this:
 

diff --git a/main/docs/authenticate/protocols/oauth.mdx b/main/docs/authenticate/protocols/oauth.mdx
@@ -8,6 +8,8 @@ title: OAuth 2.0 Authorization Framework
 'twitter:description': Learn how Auth0 works with the OAuth 2.0 Authorization Framework.
 'twitter:title': OAuth 2.0 Authorization Framework
 ---
+import {AuthLink} from "/snippets/AuthLink.jsx";
+
 <Card title="Overview">
 
 Key Concepts
@@ -132,7 +134,7 @@ The [OAuth 2.0 Multiple Response Type Encoding Practices specification](https://
 </tr>
 <tr>
 <td><code>web_message</code></td>
-<td>This response mode is defined in <a href="https://tools.ietf.org/html/draft-sakimura-oauth-wmrm-00">OAuth 2.0 Web Message Response Mode specification</a>. It uses HTML5 Web Messaging instead of the redirect for the authorization response from the /authorization endpoint. This is particularly useful when using Silent Authentication. To do this response mode, you must register your app's URL at the <strong>Allowed Web Origins</strong> field in your Auth0 <a href="https://manage.auth0.com/#/applications/{yourClientId}/settings">application settings</a>.</td>
+<td>This response mode is defined in <a href="https://tools.ietf.org/html/draft-sakimura-oauth-wmrm-00">OAuth 2.0 Web Message Response Mode specification</a>. It uses HTML5 Web Messaging instead of the redirect for the authorization response from the /authorization endpoint. This is particularly useful when using Silent Authentication. To do this response mode, you must register your app's URL at the <strong>Allowed Web Origins</strong> field in your Auth0 <AuthLink href="https://manage.auth0.com/#/applications/{yourClientId}/settings">application settings</AuthLink>.</td>
 </tr>
 </tbody>
 </table>

diff --git a/...cs/authenticate/protocols/saml/saml-configuration/customize-saml-assertions.mdx b/...cs/authenticate/protocols/saml/saml-configuration/customize-saml-assertions.mdx
@@ -10,6 +10,8 @@ title: Customize SAML Assertions
   WS-Fed protocol parameters.
 'twitter:title': Customize SAML Assertions
 ---
+import {AuthLink} from "/snippets/AuthLink.jsx";
+
 You can customize your <Tooltip tip="Security Assertion Markup Language (SAML): Standardized protocol allowing two parties to exchange authentication information without a password." cta="View Glossary" href="/docs/glossary?term=SAML">SAML</Tooltip> assertions as well as the SAML and WS-Federation protocol parameters.
 
 ## Auth0 as identity provider
@@ -18,7 +20,7 @@ Customize SAML assertions when Auth0 acts as the <Tooltip tip="Identity Provider
 
 ### Use the Dashboard
 
-1. Go to [Dashboard > Applications > Applications](https://manage.auth0.com/#/applications/{yourClientId}/addons) and select the name of the application to view.
+1. Go to <AuthLink href="https://manage.auth0.com/#/applications/{yourClientId}/addons">Dashboard > Applications > Applications</AuthLink> and select the name of the application to view.
 2. Select the **Addons** tab.
 3. Enable **SAML2 Web App** toggle to view settings and options.
 

diff --git a/...s/authenticate/protocols/saml/saml-identity-provider-configuration-settings.mdx b/...s/authenticate/protocols/saml/saml-identity-provider-configuration-settings.mdx
@@ -8,6 +8,8 @@ title: SAML Identity Provider Configuration Settings
 'twitter:description': Describes the SAML identity provider configuration settings.
 'twitter:title': SAML Identity Provider Configuration Settings
 ---
+import {AuthLink} from "/snippets/AuthLink.jsx";
+
 import {AuthCodeBlock} from "/snippets/AuthCodeBlock.jsx";
 
 import {AuthCodeGroup} from "/snippets/AuthCodeGroup.jsx";
@@ -275,11 +277,11 @@ SAML logout requests must be signed by the identity provider.
 
 Use the following links to obtain the public key in different formats:
 
-* [CER](https://{yourDomain}/cer?cert=connection)
-* [PEM](https://{yourDomain}/pem?cert=connection)
-* [raw PEM](https://{yourDomain}/rawpem?cert=connection)
-* [PKCS#7](https://{yourDomain}/pb7?cert=connection)
-* [Fingerprint](https://{yourDomain}/fingerprint?cert=connection)
+* <AuthLink href="https://{yourDomain}/cer?cert=connection">CER</AuthLink>
+* <AuthLink href="https://{yourDomain}/pem?cert=connection">PEM</AuthLink>
+* <AuthLink href="https://{yourDomain}/rawpem?cert=connection">raw PEM</AuthLink>
+* <AuthLink href="https://{yourDomain}/pb7?cert=connection">PKCS#7</AuthLink>
+* <AuthLink href="https://{yourDomain}/fingerprint?cert=connection">Fingerprint</AuthLink>
 
 Download the certificate in the format requested by the IdP.
 

diff --git a/...nticate/protocols/saml/saml-sso-integrations/sign-and-encrypt-saml-requests.mdx b/...nticate/protocols/saml/saml-sso-integrations/sign-and-encrypt-saml-requests.mdx
@@ -10,6 +10,8 @@ title: Sign and Encrypt SAML Requests
   SAML requests
 'twitter:title': Sign and Encrypt SAML Requests
 ---
+import {AuthLink} from "/snippets/AuthLink.jsx";
+
 To increase the security of your transactions, you can sign or encrypt both your requests and your responses in the <Tooltip tip="Security Assertion Markup Language (SAML): Standardized protocol allowing two parties to exchange authentication information without a password." cta="View Glossary" href="/docs/glossary?term=SAML">SAML</Tooltip> protocol. In this article, you'll find configurations for specific scenarios, separated under two use cases:
 
 * Auth0 as the SAML service provider (for example, a SAML connection)
@@ -111,11 +113,11 @@ If Auth0 is the SAML service provider, it may need to receive encrypted asserti
 
 Use the following links to obtain the public key in different formats:
 
-* [CER](https://{yourDomain}/cer?cert=connection)
-* [PEM](https://{yourDomain}/pem?cert=connection)
-* [raw PEM](https://{yourDomain}/rawpem?cert=connection)
-* [PKCS#7](https://{yourDomain}/pb7?cert=connection)
-* [Fingerprint](https://{yourDomain}/fingerprint?cert=connection)
+* <AuthLink href="https://{yourDomain}/cer?cert=connection">CER</AuthLink>
+* <AuthLink href="https://{yourDomain}/pem?cert=connection">PEM</AuthLink>
+* <AuthLink href="https://{yourDomain}/rawpem?cert=connection">raw PEM</AuthLink>
+* <AuthLink href="https://{yourDomain}/pb7?cert=connection">PKCS#7</AuthLink>
+* <AuthLink href="https://{yourDomain}/fingerprint?cert=connection">Fingerprint</AuthLink>
 
 Download the certificate in the format requested by the IdP.
 

diff --git a/main/docs/authenticate/protocols/ws-fed-protocol.mdx b/main/docs/authenticate/protocols/ws-fed-protocol.mdx
@@ -10,6 +10,8 @@ title: Web Services Federation Protocol
   (WS-Fed) protocol.
 'twitter:title': Web Services Federation Protocol
 ---
+import {AuthLink} from "/snippets/AuthLink.jsx";
+
 Web Services Federation (WS-Federation or <Tooltip tip="Web Service Federation (WS-Fed): Protocol for managing user identities across domains." cta="View Glossary" href="/docs/glossary?term=WS-Fed">WS-Fed</Tooltip>) is part of the larger WS-Security framework and an extension to the functionality of WS-Trust. The features of WS-Federation can be used directly by SOAP applications and web services. WS-Fed is a protocol that can be used to negotiate the issuance of a token. You can use this protocol for your applications (such as a Windows Identity Foundation-based app) and for <Tooltip tip="Identity Provider (IdP): Service that stores and manages digital identities." cta="View Glossary" href="/docs/glossary?term=identity+providers">identity providers</Tooltip> (such as Active Directory Federation Services or Azure AppFabric Access Control Service).
 
 ## For applications
@@ -18,7 +20,7 @@ When you register an application in Auth0, it will automatically be assigned a W
 
 `https://{yourDomain}/wsfed/{yourClientId}`
 
-You can find all available options for configuring WS-Fed under the [advanced settings](https://manage.auth0.com/#/applications/{yourClientId}/settings) area for your application.
+You can find all available options for configuring WS-Fed under the <AuthLink href="https://manage.auth0.com/#/applications/{yourClientId}/settings">advanced settings</AuthLink> area for your application.
 
 You will need to configure the **<Tooltip tip="Relying Party: Entity (such as a service or application) that depends on a third-party identity provider to authenticate a user." cta="View Glossary" href="/docs/glossary?term=Relying+Party">Relying Party</Tooltip>**, which can be done using the following metadata endpoint:
 

diff --git a/...identity-provider/configure-saml2-web-app-addon-for-github-enterprise-cloud.mdx b/...identity-provider/configure-saml2-web-app-addon-for-github-enterprise-cloud.mdx
@@ -10,6 +10,8 @@ title: Configure GitHub Enterprise Cloud as SAML Service Provider
   the SAML2 Web App addon for a GitHub Enterprise Cloud (github.com) organization.
 'twitter:title': Configure GitHub Enterprise Cloud as SAML Service Provider
 ---
+import {AuthLink} from "/snippets/AuthLink.jsx";
+
 You can configure Auth0 to serve as an <Tooltip tip="Identity Provider (IdP): Service that stores and manages digital identities." cta="View Glossary" href="/docs/glossary?term=identity+provider">identity provider</Tooltip> for [GitHub Enterprise Cloud](https://help.github.com/en/articles/about-authentication-with-saml-single-sign-on) (github.com). GitHub requires an enterprise-level subscription to enable using an external <Tooltip tip="Identity Provider (IdP): Service that stores and manages digital identities." cta="View Glossary" href="/docs/glossary?term=SAML">SAML</Tooltip> IdP.
 
 * To learn about <Tooltip tip="Single Sign-On (SSO): Service that, after a user logs into one applicaton, automatically logs that user in to other applications." cta="View Glossary" href="/docs/glossary?term=SSO">SSO</Tooltip> on GitHub, read [About authentication with SAML single sign-on](https://help.github.com/en/articles/about-authentication-with-saml-single-sign-on) on https://docs.github.com.
@@ -18,7 +20,7 @@ You can configure Auth0 to serve as an <Tooltip tip="Identity Provider (IdP): Se
 ## Configure SAML SSO on Auth0
 
 1. Go to [Dashboard > Applications > Applications](https://manage.auth0.com/#/applications) and create a new application. Give it a meaningful name like **GitHub**. You can choose any application type, but the **Regular Web App** type is recommended.
-2. Go to the [Addons](https://manage.auth0.com/#/applications/{yourClientId}/addons) tab and enable the **SAML2 Web App** toggle.
+2. Go to the <AuthLink href="https://manage.auth0.com/#/applications/{yourClientId}/addons">Addons</AuthLink> tab and enable the **SAML2 Web App** toggle.
 3. On the **Settings** tab, set the **Application Callback URL** to: `https://github.com/orgs/{YOUR_GITHUB_ORG_NAME}/saml/consume`.
 
    <Frame>![Dashboard Applications Applications Addons Tab SAML2 Web App Settings Tab](/docs/images/cdy7uua7fh8z/6dJgYkcOgMZ73HVTkAWt1x/fe9dbbf306e6c587cb3326c00a3b4e1f/2025-02-27_13-59-00.png)</Frame>

diff --git a/...dentity-provider/configure-saml2-web-app-addon-for-github-enterprise-server.mdx b/...dentity-provider/configure-saml2-web-app-addon-for-github-enterprise-server.mdx
@@ -10,12 +10,14 @@ title: Configure GitHub Enterprise Server as SAML Service Provider
   the SAML2 Web App addon for a GitHub Enterprise Server private instance.
 'twitter:title': Configure GitHub Enterprise Server as SAML Service Provider
 ---
+import {AuthLink} from "/snippets/AuthLink.jsx";
+
 You can configure Auth0 as the <Tooltip tip="Identity Provider (IdP): Service that stores and manages digital identities." cta="View Glossary" href="/docs/glossary?term=identity+provider">identity provider</Tooltip> using the SAML2 Web App addon for [GitHub Enterprise Server](https://help.github.com/en/enterprise/2.16/admin/user-management/using-saml) (i.e. your private GitHub appliance). If you are looking for instructions to set up Auth0 as the identity provider for GitHub Enterprise Cloud (github.com), read [Configure Auth0 as Identity Provider for GitHub Enterprise Cloud](/docs/authenticate/single-sign-on/outbound-single-sign-on/configure-auth0-saml-identity-provider/configure-saml2-web-app-addon-for-github-enterprise-cloud) instead.
 
 ## Configure SAML SSO on Auth0
 
 1. Go to [Dashboard > Applications > Applications](https://manage.auth0.com/#/applications) and create a new application. Give it a meaningful name like **GitHub**. You can choose any application type, but the **Regular Web App** type is recommended.
-2. Go to the [Addons](https://manage.auth0.com/#/applications/{yourClientId}/addons) tab and enable the **SAML2 Web App** toggle.
+2. Go to the <AuthLink href="https://manage.auth0.com/#/applications/{yourClientId}/addons">Addons</AuthLink> tab and enable the **SAML2 Web App** toggle.
 3. On the **Settings** tab, set the **Application Callback URL** to : `https://github.com/orgs/{yourGitHubOrgName}/saml/consume`.
 
    <Frame>![Dashboard Applications Applications Addons Tab SAML2 Web App Settings Tab](/docs/images/cdy7uua7fh8z/6dJgYkcOgMZ73HVTkAWt1x/fe9dbbf306e6c587cb3326c00a3b4e1f/2025-02-27_13-59-00.png)</Frame>

diff --git a/main/docs/customize/extensions/ad-ldap-connector-health-monitor.mdx b/main/docs/customize/extensions/ad-ldap-connector-health-monitor.mdx
@@ -10,6 +10,8 @@ title: Auth0 AD/LDAP Connector Health Monitor Extension
   Monitor extension.
 'twitter:title': Auth0 AD/LDAP Connector Health Monitor Extension
 ---
+import {AuthLink} from "/snippets/AuthLink.jsx";
+
 The Auth0 AD/LDAP Connector Health Monitor exposes an API endpoint of your choice so that you can monitor your AD/LDAP connectors.
 
 ## Configure the extension
@@ -19,7 +21,7 @@ To install and configure this extension:
 1. Navigate to [Auth0 Dashboard > Extensions](https://manage.auth0.com/#/extensions), and select **Auth0 AD/LDAP Connector Health Monitor**. The **Install Extension** window opens.
 2. Set the following configuration parameters, and select **Install**:
 
-* **Auth0_Domain**: The domain for your Auth0 application, which you can find in your [Auth0 Application Settings](https://manage.auth0.com/#/applications/{yourClientId}/settings).
+* **Auth0_Domain**: The domain for your Auth0 application, which you can find in your <AuthLink href="https://manage.auth0.com/#/applications/{yourClientId}/settings">Auth0 Application Settings</AuthLink>.
 * **Auth0_Global_Client_ID**: The Global <Tooltip tip="Client ID: Identification value given to your registered resource from Auth0." cta="View Glossary" href="/docs/glossary?term=Client+ID">Client ID</Tooltip> for your Auth0 application, which you can find in the **Global Application Information** section of your [Tenant Advanced Settings](https://manage.auth0.com/#/tenant/advanced).
 * **Auth0_Global_Client_Secret**: The Global <Tooltip tip="Client Secret: Secret used by a client (application) to authenticate with the Authorization Server; it should be known to only the client and the Authorization Server and must be sufficiently random to not be guessable." cta="View Glossary" href="/docs/glossary?term=Client+Secret">Client Secret</Tooltip> for your Auth0 application, which you can find in the **Global Application Information** section of your [Tenant Advanced Settings](https://manage.auth0.com/#/tenant/advanced).
 

diff --git a/main/docs/customize/integrations/azure-api-management.mdx b/main/docs/customize/integrations/azure-api-management.mdx
@@ -10,6 +10,8 @@ title: Integrate with Azure API Management
   access to an API managed by the Azure API Management service
 'twitter:title': Integrate with Azure API Management
 ---
+import {AuthLink} from "/snippets/AuthLink.jsx";
+
 <Card title="Before you start">
 
 You'll need a Microsoft account with access to the [Azure Portal](https://azure.microsoft.com/).
@@ -176,15 +178,15 @@ To use Auth0 to secure your Azure API, you'll need to register Auth0 as an OAuth
    </tr>
    <tr>
    <td><strong>Authorization endpoint URL</strong></td>
-   <td>Refer to your tenant's <a href="https://{yourDomain}/.well-known/openid-configuration">OIDC Discovery endpoint</a> and append the <code>audience</code> parameter. For example: `https://{yourDomain}/authorize?audience={API_AUDIENCE}`.</td>
+   <td>Refer to your tenant's <AuthLink href="https://{yourDomain}/.well-known/openid-configuration">OIDC Discovery endpoint</AuthLink> and append the <code>audience</code> parameter. For example: `https://{yourDomain}/authorize?audience={API_AUDIENCE}`.</td>
    </tr>
    <tr>
    <td><strong>Authorization request method</strong></td>
    <td>Default is <code>GET</code>.</td>
    </tr>
    <tr>
    <td><strong>Token endpoint URL</strong></td>
-   <td>Refer to your tenant's <a href="https://{yourDomain}/.well-known/openid-configuration">OIDC Discovery endpoint</a> .</td>
+   <td>Refer to your tenant's <AuthLink href="https://{yourDomain}/.well-known/openid-configuration">OIDC Discovery endpoint</AuthLink> .</td>
    </tr>
    <tr>
    <td><strong>Client authentication methods</strong></td>