---
title: "Global Extension Configuration"
manual: "Klaro! Consent Manager"
version: "3.0"
permalink: "https://docs.typo3.org/permalink/erhaweb/klaro-consent-manager:configuration-extension-configuration@3.0"
source: "Configuration/ExtensionConfiguration/Index.rst"
rendered: "2026-09-24T10:59:28+00:00"
---

# Global Extension Configuration {#configuration-extension-configuration}

The global extension configuration is defined in `ext_conf_template.txt`.
It is independent of the site-specific Klaro configuration record and applies
to global frontend integration details of the extension.

## Backend path {#backend-path}

| TYPO3 v13 | TYPO3 v14 |
| --- | --- |
| **Admin Tools** → **Settings** → **Extension Configuration** | **System** → **Settings** → **Extension Configuration** |

## Settings {#settings}

-   **replaceUrl.show**

    -   *type:* string
    -   *Default:* `https://KLARO_CONSENT.com`

    Frontend links with this exact `href` value are replaced by the
    `ReplaceBeforeOutput` middleware with a Klaro trigger link that opens the
    consent manager. See [Trigger Links](https://docs.typo3.org/permalink/erhaweb/klaro-consent-manager:features-trigger-links@3.0) for the feature
    overview.

-   **replaceUrl.reset**

    -   *type:* string
    -   *Default:* `https://KLARO_RESET.com`

    Frontend links with this exact `href` value are replaced by the
    `ReplaceBeforeOutput` middleware with a Klaro trigger link that resets the
    consent state and opens the consent manager. See
    [Trigger Links](https://docs.typo3.org/permalink/erhaweb/klaro-consent-manager:features-trigger-links@3.0) for the feature overview.

-   **klaroConfigurationPath**

    -   *type:* string
    -   *Default:* `/klaro-config.js`

    If this value is not empty, the active Klaro configuration is exposed as
    JavaScript at this path and loaded before the Klaro JavaScript library. The
    default endpoint is `/klaro-config.js`. See
    [Standalone configuration](https://docs.typo3.org/permalink/erhaweb/klaro-consent-manager:features-standalone-configuration@3.0) for the feature overview.

    This endpoint is useful when the Klaro configuration managed in TYPO3
    should be consumed by another application. It can also be set to an empty
    value to use the backwards-compatible inline configuration fallback.

    After changing this value, flush TYPO3's system caches so the generated
    site routing configuration is rebuilt.