fastpluggy-auth-user 0.2.7

User Authentication plugin for Fastpluggy

Auth User Plugin

The Auth User plugin provides comprehensive user authentication and management functionality for FastPluggy applications.

📊 Current Status

✅ PRODUCTION READY FEATURES:

• Complete admin interface for user management (CRUD operations)
• User authentication with secure password hashing
• Session management with configurable expiration
• User profile pages with authentication protection
• Automatic admin user creation on first install
• Menu integration for user functions

⚠️ PARTIALLY IMPLEMENTED:

• Login routes (exist but commented out - ready for activation)

📋 ROADMAP: See Implementation Roadmap for detailed development plan.

Features

• User Authentication: Secure username/password authentication with BCrypt hashing
• Admin Interface: Complete user management with list, add, edit functionality
• Session Management: Configurable session handling with JSON data storage
• User Profiles: Protected profile pages for authenticated users
• Menu Integration: Automatic menu items for profile and logout
• Template System: Jinja2 templates for login and profile pages
• Database Integration: SQLAlchemy models with FastPluggy core

Models

FastPluggyBaseUser

The main user model with the following fields:

• username: Unique username (String, 255 chars)
• hashed_password: Securely hashed password (String, 255 chars)
• is_admin: Boolean flag indicating admin privileges (default: False)

Session

Session management model for user authentication:

• session_id: Unique session identifier (String, 255 chars)
• session_data: JSON data stored in the session
• session_lifetime: Session expiration timestamp
• session_time: Session creation timestamp
• ip: Client IP captured at login (nullable; only set when collect_login_ip is enabled)
• user_agent: Raw User-Agent captured at login (nullable)
• last_seen_at: Last activity timestamp, refreshed (throttled) on authenticated requests (nullable)

Session management

Both authenticated users and admins can review and revoke sessions:

• Self-service — GET /profile/sessions/ lists the current user's active sessions with device (heuristic User-Agent parse), IP, relative last-seen, created/expires. Revoke a single session or "revoke all other sessions". The IP column is hidden entirely when collect_login_ip is disabled.
• Admin-wide — GET /admin/users/sessions/ (requires the fp_admin role) lists every active session across all users with a username filter, and can revoke any individual session or all of a given user's sessions.

last_seen_at is refreshed inside the authentication path but throttled to at most one write per session_last_seen_throttle seconds, and is wrapped so a tracking failure can never break authentication. Set session_track_metadata to false to disable User-Agent capture and last-seen tracking entirely.

Configuration

The plugin uses AuthUserConfig class with the following settings:

from fastpluggy.core.config import BaseDatabaseSettings
from typing import Optional, Literal

class AuthUserConfig(BaseDatabaseSettings):
    # Set to None to enable UI-based setup on first install
    # If None, admin user creation will be handled via setup UI
    default_admin_username: Optional[str] = None
    default_admin_password: Optional[str] = None

    # Auth backend: "session" (cookies + tokens + login redirect) or "basic" (HTTP Basic popup)
    auth_backend: Literal["session", "basic"] = "session"

    login_template: str = 'auth_user/login.html'
    collect_login_ip: bool = True
    allow_api_tokens: bool = True  # set to False to disable personal access tokens globally

    # Per-session metadata (device / IP / last-seen on the sessions pages)
    session_track_metadata: bool = True   # capture user-agent + refresh last_seen_at
    session_last_seen_throttle: int = 60  # min seconds between last_seen_at writes

Setting	Default	Effect
collect_login_ip	True	Capture client IP at login; gates the IP column on the sessions pages
session_track_metadata	True	Capture User-Agent at login and refresh last_seen_at on activity
session_last_seen_throttle	60	Minimum seconds between last_seen_at writes (keeps the auth path cheap)

Auth backends

Backend	auth_backend	How it works
Session (default)	"session"	Cookie-based sessions + Bearer tokens + HTTP Basic with __token__ (pip/twine). Redirects to login page on auth failure.
Basic	"basic"	HTTP Basic authentication only. Triggers browser popup on auth failure.

The auth backend is configurable via environment variable or database settings:

AUTH_USER_AUTH_BACKEND=basic  # or "session" (default)

Admin User Setup

The plugin provides intelligent admin user setup with two approaches:

🎯 Recommended: UI-Based Setup (Default)

By default, default_admin_username and default_admin_password are set to None, which enables the setup UI:

1. First Install: When no users exist, visit /setup/ to create the first admin user
2. Secure: No hardcoded credentials - you choose the username and password
3. User-Friendly: Clean web interface with validation and error handling
4. Automatic Detection: The system automatically detects when setup is needed

🔧 Alternative: Automatic Creation with Configured Credentials

If you prefer automatic admin creation, configure default credentials:

# In your environment or config
default_admin_username = "your_admin_username"
default_admin_password = "your_secure_password"

When configured, the plugin will automatically create the admin user on first startup.

📋 Setup Process

1. Plugin Load: System checks if any users exist
2. If No Users:
   • With configured credentials: Automatically creates admin user
   • Without credentials (default): Logs message to visit /setup/
3. Setup UI: Visit /setup/ to create admin user with custom credentials
4. Redirect: After successful setup, redirects to login page

🔍 Setup Status Check

You can check if setup is needed programmatically:

from fastpluggy_plugin.auth_user.src.repository import needs_initial_setup
from fastpluggy.core.database import get_db

if needs_initial_setup(get_db()):
    print("Setup required - visit /setup/")
else:
    print("Admin user exists")

Routes

Setup Routes

• GET /setup/ - Initial admin user setup page (only accessible when no users exist)
• POST /setup/ - Process admin user creation form
• GET /setup/check - API endpoint to check if setup is needed

Authentication Routes

• GET /logout - Logout user and clear session

Profile Routes

• GET /profile/ - User profile page (requires authentication)

Menu Integration

The plugin automatically adds the following menu items:

• Profile (/profile/) - User profile page
• Logout (/logout) - Logout functionality

Templates

The plugin expects the following Jinja2 templates:

• auth_user/profile.html.j2 - User profile page template
• auth_user/login.html.j2 - Login page template (referenced in config)

Usage

1. Install the plugin — it is auto-discovered via the fastpluggy.plugins entry point
2. Auth is auto-wired — the plugin calls fast_pluggy.set_auth_manager() during on_load_complete, so you do not need to pass auth_manager= to FastPluggy(). Just FastPluggy(app) is enough.
3. First run — visit /setup/ to create the first admin user (or set default_admin_username / default_admin_password in config for automatic creation)
4. Profile — authenticated users can manage their profile at /profile/

If you pass auth_manager= explicitly to FastPluggy(), the plugin respects it and does not override.

Personal Access Tokens

Users can create long-lived API tokens for programmatic access (CI/CD, pip, twine, scripts).

Managing tokens

Tokens are managed via the UI at /tokens/:

• Create a token with a name and optional expiry (in days)
• The raw token value is shown once — copy it immediately
• Revoke any token at any time

Using tokens — API clients (Bearer)

Authorization: Bearer <your-token>

Any endpoint protected by require_authentication accepts this header.

Using tokens — pip / twine (HTTP Basic)

pip and twine use HTTP Basic auth. Use __token__ as the username and your token as the password:

# pip install
pip install --index-url https://__token__:<your-token>@registry.fastpluggy.xyz/pypi/simple/ my-package

# twine upload
twine upload --repository-url https://registry.fastpluggy.xyz/pypi/ \
  -u __token__ -p <your-token> dist/*

Or configure ~/.pypirc:

[fastpluggy]
repository = https://registry.fastpluggy.xyz/pypi/
username = __token__
password = <your-token>

SessionAuthManager detects the __token__ username in Basic auth headers and validates the password as a personal access token (SHA256 hash lookup), so no separate auth scheme is needed for pip/twine.

Token model

Field	Description
name	User-friendly label
token_hash	SHA256 of the raw token (never stored in plaintext)
expires_at	Optional expiry timestamp
last_used_at	Updated on every successful use

Security Notes

• Passwords are securely hashed using BCrypt (BasicAuthManager.hash_password())
• Sessions are managed with configurable lifetime (default: 1 hour)
• Admin privileges are controlled via the is_admin boolean field
• API tokens are stored as SHA256 hashes (never in plaintext)
• Important: Change the default admin password after first login for security