magic-link-auth-companion

You can revoke a magic link token using the provided CLI utility. This tool allows you to instantly revoke a specific token or all active tokens, overriding their configured TTL and invalidating access across your backend and dashboard.

HMAC-SHA256 signing secures magic link authentication by generating a cryptographic signature for each token. This singleton service validates the signature against backend storage to prevent tampering and unauthorized access.

Yes, the service synchronizes magic link configurations between Redis-backed storage and external backends. This ensures that TTL enforcement and revocation workflows consistently update API responses and UI behavior across systems.

The best way to enforce token TTL for magic links is by using a singleton service with configurable expiration settings. It automatically manages token validation and synchronization across Redis and external backends.

Redis is used as the primary storage backend for synchronizing token states. The service also performs environment validation to ensure secure HMAC-SHA256 signing and TTL enforcement before executing revocation workflows.

A singleton service limits magic link authentication to a single active instance per process. While it ensures consistent HMAC-SHA256 signing and TTL enforcement, you must manage synchronization carefully across distributed backend environments.