Skip to content

enno.dev Commerce Partner

  • Home
  • Shopware 5
  • Shopware 6
  • English
    • Deutsch
    • English

Shopware 5

10
  • Awin Conversion Tracking, Remarketing and Server-to-Server Tracking
  • Empty Cart Button
  • ESD Multi-Download
  • Exclude Search Terms or Redirect Terms to Pages
  • Global Price Changes
  • Preselected Filters
  • Properties AND Operation in the Filters
  • Redeemable Vouchers per Customer Also for Guest Orders
  • Registration Filter Against Spam Registrations
  • Tabs Advanced: Manage All Tabs in One Place

Shopware 6

11
  • Debug for Productive Systems
  • Digital Products and Downloads (ESD)
  • Empty Cart Button
  • Import with Article Numbers: Update Products via Product Number
  • Product Link Instead of Shopping Cart Button
  • Registration Filter Against Spam Registrations
  • Sentinel Admin Security: 2FA, Login Lock, File Type Check
  • Tabs Advanced: Manage All Tabs in One Place
  • Tabs Advanced Extension: Anchor Tabs with Jump Marks
  • Tabs Advanced Extension: Output Entity Custom Fields as Links
  • Tabs Advanced Extension: Product Detail Page Layout Assignment
View Categories
  • Shopware 6
  • Sentinel Admin Security: 2FA, Login Lock, File Type Check

Sentinel Admin Security: 2FA, Login Lock, File Type Check

Version 2.2.0 Shopware from 6.7.14 As of November 3, 2026

Sentinel protects the Administration of your shop. A code from an authenticator app is added to the password, an IP address with too many failed attempts is locked, the Administration optionally moves from /admin to an address of your own and uploads are checked for their actual file type.

Older versions of the plugin without two-factor authentication are available for Shopware 6.5 to 6.7.13. This guide describes version 2.2.0.

View in the Shopware Store

What the plugin does #

Two-factor authentication #

After the password, admin users enter a six-digit code from an authenticator app, for example Google Authenticator, Microsoft Authenticator or 1Password. Instead of the code, one of ten backup codes also works, each of them once. The user is logged in only when both are correct.

Each user sets up two-factor authentication themselves, in their profile on the "Security" tab. There they also renew the backup codes or remove two-factor authentication again. Setting it up ends all of the user's sessions that began without a code, so the user logs in again once.

You can make two-factor authentication mandatory for administrators or for all users, with a grace period. Anyone who has not set it up after that is guided through the setup at login. Wrong codes are limited per account: after five failed attempts there is a 15-minute wait, after each further five twice as long, up to one day.

If a user has lost their smartphone, an administrator resets the two-factor authentication in the user's details. The user list shows who has set it up. Users with the permission "Reset two-factor authentication of other users" may also reset it.

IP lock after failed attempts #

After the configured number of failed logins, the IP address is locked out of the Administration and the Admin API for 30 minutes. Each further failed attempt after a lock extends the next lock by 30 minutes. A successful login resets the counter, as do 24 hours without a failed attempt and without an active lock. The Storefront stays reachable. Addresses from the list of exceptions are never locked.

IP addresses are stored only for the lock and for the last successful login. A scheduled task deletes all entries daily that have been unchanged for 30 days.

Custom admin URL #

Instead of under /admin, you reach the Administration under a path of your own, for example /backoffice. After that it is no longer reachable under /admin.

File check on upload #

The media management rejects files whose content does not match the file extension, for example a PDF document that was renamed to .jpg.

Installation and setup #

  1. Install the plugin under Extensions > My extensions and activate it.
  2. Open the configuration of "Sentinel Admin Security" there.
  3. Under "Login protection", leave the IP lock switched on and set the number of allowed failed attempts. Under "IP exceptions", enter the addresses of your office or your agency.
  4. First set up your own two-factor authentication: user menu at the bottom left, your profile, "Security" tab.
  5. Then define under "Two-factor authentication" for whom it is mandatory and how long the grace period is.
  6. If nobody in your team works with personal API keys, switch on "Block all personal API access keys" under "API access".
  7. If you want a custom admin URL, select "All Sales Channels" at the top, enter the path under "Custom admin path" and save. Write down the new address beforehand.

For stored IP addresses to be deleted, the scheduled tasks and the message worker of the shop must be running. If the shop is behind a load balancer or CDN, configure TRUSTED_PROXIES so that Shopware sees the IP address of the visitor and not that of the proxy.

Settings #

The settings for two-factor authentication and the admin URL apply to the whole shop and can only be changed under "All Sales Channels".

SettingDefaultEffect
Lock IP addresses after failed admin loginsonSwitches on the IP lock.
Allowed failed login attempts3The failed attempt after the last allowed one locks the address for 30 minutes.
IP exceptionsemptyAddresses that are never locked, separated by comma, semicolon or space. Ranges are not supported.
Two-factor authentication for admin usersOptionalOff, Optional, Required for administrators or Required for all users.
Grace period in days7How long a user can still log in without a code. The period starts with the user's first login after the requirement took effect. 0 means setup at the next login.
Also ask for the code when the password is confirmedoffShopware asks for the password again before changes to users, roles or your own profile. When this is switched on, the code is required there as well.
Block all personal API access keysoffRefuses every personal API key, including existing ones. Integrations keep working.
Custom admin pathemptyReplaces /admin. 3 to 64 characters: letters, digits, hyphen and underscore, starting with a letter or a digit.
Check file type on uploadonRejects uploads whose content does not match the extension. Switch this off only if a correct file is rejected.

Changing two-factor authentication from "Off" to another level logs out all users who have set it up. Their sessions only continue after a login with the code.

Personal API keys #

A personal API key acts as its user, without a password and without a second factor. That is why Sentinel refuses the keys of all users for whom two-factor authentication is mandatory, even during the grace period. With the switch "Block all personal API access keys" this applies to everyone. Automations that should keep running use an integration under Settings > System > Integrations.

If a key has fallen into the wrong hands, blocking it is not enough. Delete the key in the user's settings, check integrations and users and change the user's password.

Custom admin URL #

The path is written to the file .env in the root directory of the shop as SHOPWARE_ADMINISTRATION_PATH_NAME. If you clear the field, the Administration is reachable under /admin again. If the variable is already set in .env.local, .env.local.php or in the server environment, the plugin reports this instead of saving.

The file .env must be writable. If the shop runs on several application servers, each of them has its own .env. In that case set the variable in the deployment.

Locked out? #

If nobody can log in anymore, for example because the only administrator has lost both the smartphone and the backup codes, reset that user's two-factor authentication on the server:

php bin/console enno-sentinel:mfa:reset benutzername

With --all instead of a user name you reset everyone. If two-factor authentication is mandatory, the user sets it up again at the next login.

If the login itself no longer works, for example because the code dialog is missing after a Shopware update, switch off two-factor authentication or deactivate the plugin:

php bin/console system:config:set EnnoSentinel.config.mfaPolicy off
php bin/console plugin:deactivate EnnoSentinel
php bin/console cache:clear

Frequently asked questions #

What happens if the APP_SECRET of the shop changes?

The two-factor keys and the backup codes depend on the APP_SECRET. If it changes, neither the authenticator apps nor the backup codes work. In that case reset everyone with enno-sentinel:mfa:reset --all. The users then set up two-factor authentication again.

How does the plugin behave with single sign-on?

With a login via single sign-on, the identity provider handles the second factor. Sentinel asks for the code only for logins with a password and does not end running sessions of users without two-factor authentication. Personal API keys also bypass the identity provider, so the plugin refuses them here as well according to the rule above.

Does a wrong code count toward the IP lock?

No. A correct password with a missing or wrong code does not count toward the IP lock. Instead, wrong codes are limited per account.

What happens when I uninstall the plugin?

A custom admin URL set through the plugin is removed from the .env. The Administration is then reachable under /admin again. This also applies if you choose to keep the user data. Without this option, uninstalling deletes all two-factor setups. If the .env is not writable, delete the line SHOPWARE_ADMINISTRATION_PATH_NAME by hand and clear the cache.

Update notes #

Update to 2.2.0 #

  • Two-factor authentication is new. By default it is optional, so nobody has to set it up after the update.
  • The IP lock no longer affects the Storefront. Stored IP addresses are deleted after 30 days.
  • The admin URL takes effect immediately without clearing the cache and is removed when you uninstall the plugin.
  • The upload check examines the content of the file. Office and Windows Media files are no longer wrongly rejected.
  • Requires Shopware 6.7.14 or later.

All changes per version are listed in the changelog on the plugin's page in the Shopware Store.

Help #

If this guide does not answer your question, write to us via the contact form on enno.dev.

Contents
  • What the plugin does
    • Two-factor authentication
    • IP lock after failed attempts
    • Custom admin URL
    • File check on upload
  • Installation and setup
  • Settings
  • Personal API keys
  • Custom admin URL
  • Locked out?
  • Frequently asked questions
  • Update notes
    • Update to 2.2.0
  • Help

enno.dev Commerce Partner

Shopware plugins
  • Shopware 6
  • Shopware 5
  • All plugins in the Shopware Store
Contact
  • Contact form
  • enno.dev
  • Commerce Partner
Legal
  • Imprint
  • Privacy Policy