Standalone access 

The standalone app at /t3vault/ can be opened without TYPO3. This is intended for disaster recovery when the CMS is broken.

Enable marker 

Standalone password login is locked until a marker file exists (same idea as TYPO3's ENABLE_INSTALL_TOOL). Like TYPO3, the marker lives outside the web root:

var/t3vault/ENABLE_T3VAULT
Copied!

Rules:

  • File missing → login locked
  • File contains KEEP_FILE → permanently enabled
  • Otherwise → enabled for one hour after the file's modification time; the window is extended on every authenticated request (sliding window)
  • Ten failed login attempts consume the marker (logged in var/t3vault/state/auth.log)

After a successful standalone login the marker is removed (unless it contains KEEP_FILE).

T3Vault lock screen asking the operator to create var/t3vault/ENABLE_T3VAULT

Standalone login stays locked until the enable marker exists.

T3Vault standalone login form for the standalone password

Password login used for disaster recovery outside the TYPO3 backend.

Backend SSO 

When you open the module while logged in as a TYPO3 administrator, T3Vault issues a short-lived one-time claim ticket (?sso=… on the iframe URL). The embedded app redeems it via /auth/backend-claim and receives a backend session — without ENABLE_T3VAULT or the standalone password. The ticket is opaque, single-use and TTL-bound (not the former HMAC bt in the URL).