Libraries tagged by auto-login

The simple auth(login,signup,forgot) with powerful extension for the Yii2 framework

Go to Download

this is wechat auth login

Go to Download

Go to Download

Log into the MediaWiki installation using IPB user accounts.

Go to Download

Authentication Page Plugin for the just-core eco system

Go to Download

This is the original auth flow for Laravel, just brought to the package environment.

Go to Download

基于laravel5.5的 微信公众号登录

Go to Download

Full Laravel User Activity + Audit Log Package (Trait Based Auto Logging)

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

Dead simple header based auth login for Wordpress

Go to Download

Quick auth & login

Go to Download

Symfony bundle to enable auto logging doctrine entity changes.

Go to Download

Auth — login, registro e recuperacao de senha para PHP sem framework: password_hash nativo, sessao segura, mensagens pt/en/es. Integra com iscos/voodoo-2026 (banco) e iscosta77/validators.

Go to Download

Voodoo Tools — ferramentas de reuso para quem programa PHP sem framework: Image (crop com posicionamento, WebP, marca d'agua), Validator e Auth (login + esqueci minha senha). Zero dependencias (so ext-gd).

Go to Download

Symfony bundle to enable auto logging doctrine entity changes.

Go to Download