TYPO3¶
The extension for TYPO3 protects the login in the backend, the login in the frontend with EXT:felogin, and the forms of the EXT:form form framework.
Requirements¶
The following requirements must be met:
| Requirement | Value |
|---|---|
| TYPO3 | version 14 |
| Extensions | felogin for the login in the frontend, form for the form framework |
| Permission | Administration rights in TYPO3 |
Install the extension¶
Proceed as follows to install the extension:
Extensions module with the open form for the upload
- ► In the Integration view, click on the Download zip button.
- ► In TYPO3, open the System → Extensions module.
- ► Click on the Upload Extension button.
- ► Select the archive and click on the Upload button.
- ↳ TYPO3 shows Extension Upload and puts the extension in the Installed Extensions list. The extension is not enabled yet.
Installed Extensions list after the upload
- ► In the A/D column, click on the icon adjacent to the EU-Captcha extension.
- ► Confirm the prompt.
- ↳ TYPO3 reloads the backend.
- ➔ The extension is enabled.
Installed Extensions list with the enabled extension
Embed the TypoScript¶
The TypoScript loads the script of the widget on each page in the frontend and adds the widget to the login form of felogin. Add this line to the TypoScript file of your website, for example typo3conf/sites/main/setup.typoscript:
From TYPO3 14, the TypoScript of a website comes from a site set. The Sites → TypoScript module only shows the definitions and gives the note that they are changed in the file system.
TypoScript module with the note about the site set
Store the credentials¶
Proceed as follows to store the credentials:
EU-Captcha module without credentials
- ► In TYPO3, open the System → EU-Captcha module.
- ► Click on the Quick Setup button and log in. As an alternative, enter the public sitekey in the Public Sitekey field and the secret in the Secret field manually. The two values are shown in the Details view of the sitekey.
- ► Click on the Save Changes button.
- ➔ The extension saves the credentials.
EU-Captcha module with the saved credentials
Note
The Save & Test button saves the credentials and additionally examines them against the API.
Note
The login in the backend of TYPO3 is protected as soon as the sitekey and the secret are saved. You cannot switch this verification off.
Select the forms¶
Protected Destinations area with the two selected destinations
In the Protected Destinations area, you select the protected forms. While no destination is selected, TYPO3 shows the Select at least one destination to activate protection. note.
| Option | Range |
|---|---|
| TYPO3 Frontend Login (EXT:felogin) | Protects the login form of felogin. The widget is added automatically with the TypoScript. |
| TYPO3 Form Framework (EXT:form) | Verifies the transmission of forms from EXT:form. In the YAML definition of the form, enter the EuCaptcha finisher as the first finisher, so that errors are shown immediately in the form. |
Then click on the Save Destinations button.
Options of the API¶
These options are available:
| Option | Effect |
|---|---|
| Check CDN/Proxy Headers | Reads the true IP address of the visitor from the headers of the system in front. Activate the option if TYPO3 is behind a CDN or a load balancer. |
| Failsafe Mode | Permits a transmission if the API of Myra EU CAPTCHA is not reachable. |
Appearance of the widget¶
These options control the appearance:
| Option | Default | Effect |
|---|---|---|
| Theme | Light | Light or dark appearance, values Light and Dark. |
| Height (px) | empty | Fixed height in pixels, minimum 48. With an empty field, the default value is applicable. |
| Width (px) | empty | Fixed width in pixels, minimum 1. With an empty field, the default value is applicable. |
Click on the Save Changes button to save the appearance.
Content Security Policy¶
The extension supplies its own Content Security Policy. This policy permits the script-src directive for the https://cdn.eu-captcha.eu address in the backend and in the frontend.
The supplied policy contains the frame-src and connect-src directives only for the backend. If you use a Content Security Policy in the frontend, then add these two directives. Without this addition, the script loads, but the hidden iframe stays empty.
Test the integration¶
Integration Test view with the Fully Integrated result
After the setup, go to the Integration Test view of the sitekey and examine the embedding.







