Libraries tagged by page_password

Authsystem with username and password for a given cms page area.

Go to Download

Symfony HttpClient client for the WordPress REST API (wp/v2) — posts, pages, media, taxonomies and custom post types, with multi-site configuration and Application Password auth.

Go to Download

Two-factor passphrase+password admin authentication guard for any admin-restricted Laravel page (Horizon, Telescope, Pulse, custom routes, etc.).

Go to Download

Build a fully custom headless storefront - your own web app, mobile app, or POS - against a single OE Commerce store. Every endpoint below is namespaced under `/api/v1/store/...`. Building admin/back-office tooling instead? See [/docs/admin](/docs/admin). New here? [/guides/store](/guides/store) walks through getting a key, the anonymous cart session, and calling your first endpoints step by step - this page is the field-level reference to come back to afterward. ## Getting Started 1. Click the **Authorize** button at the top of this page. 2. Provide credentials: - **X-Commerce-Key** (always required) - your store's Store Access Key from Backoffice > Settings > Application APIs. `pk_store_...` (publishable) is safe for browser/mobile code; `sk_store_...` (secret) is server-to-server only and is rejected outright if a browser Origin header is present. - **Bearer** (only for endpoints acting on a specific customer - Account, Orders, Wishlists, etc.) - the token from **Auth > register** or **Auth > login**. Once authorized, you can explore and test all available endpoints directly from this interface. ## Anonymous Carts A guest cart is tracked by an `X-Session-Ref` header, not a cookie - the server generates one on your first request and echoes it back on every response after. Keep sending back whatever value you last received. Logging in carries that same cart forward onto the customer's account automatically, with no separate merge step. ## Errors Failures use RFC 9457 Problem Details (`application/problem+json`) with a stable `code` field for programmatic handling, e.g. `store_key_invalid`, `store_key_revoked`, `store_key_scope_denied`, `rate_limited`. A rejected *business* action (e.g. adding fewer than a product's minimum order quantity to the cart) instead comes back as HTTP 200 with `"success": false` and a human-readable `message` - always check `success` in the body, not just the HTTP status code. ## Rate Limits Requests are limited per Store Access Key (200/minute). The credential-stuffing surface (register/login/forgot-password/reset-password) is limited more tightly per caller IP (10 per 5 minutes). A 429 response includes a `Retry-After` header.

Go to Download

One-command Laravel Inertia auth boilerplate (register, login, logout, change password, forgot/reset password, email verification) with a session-based AuthController, routes, and React/Tailwind pages installed automatically.

Go to Download

A set of pages and transactional emails for user login, signup and password reset

Go to Download

This extension provides integration with page_password to output content from TYPO3 in JSON format.

Go to Download

A simple plugin that allows you to password protect a page.

Go to Download

Create password protected pages.

Go to Download

iMi Password Protected Pages

Go to Download

Create password protected pages.

Go to Download

Password protect any page on the CMS.

Go to Download

Simple password protection for individual pages

Go to Download

Extends the default Contao 'Lost password' front end module to allow forwarding users to a alternative page for setting their new password

Go to Download

Protect pages or private files by password

Go to Download