Filament Access Secret Laravel Package

Product Decisions This Supports

• Admin surface exposure strategy — decides whether the Filament panel is publicly reachable, IP-restricted, or gated behind a shared secret during early access and internal rollout.
• Build vs. buy for lightweight gating — replaces a hand-rolled middleware with a small, MIT-licensed package; the tradeoff is a one-line install versus a low-star (38), single-maintainer dependency.
• Roadmap sequencing — lets you ship the admin panel before SSO, RBAC, and MFA are ready, decoupling "the admin exists" from "the admin is fully secured." This is a schedule-compression decision, not a security-architecture decision.
• Use-case fit — staging and demo environments, client previews, internal ops tools, MVP panels, and short-term contractor access are the natural fits.
• Risk acceptance criteria — forces an explicit call on whether a URL-borne secret is an acceptable compensating control given that secrets leak through browser history, referrer headers, proxy/CDN logs, and pasted links.
• Dependency governance — a 38-star package warrants a pin-and-review decision (fork, vendor, or accept upstream risk) before it lands in a production path.

When to Consider This Package

Consider it when:

• A Filament panel is reachable from the public internet and SSO/RBAC is weeks or months out.
• The environment is staging, demo, pre-launch, or an internal-only tool with a small, known user set.
• You need a stopgap measured in weeks, with a committed plan to replace it with real authentication.
• The team can absorb a low-star dependency (pin the version, read the ~small source, keep an exit path).
• The alternative is no gate at all — the bar to clear is "better than an open /admin," not "better than SSO."

Look elsewhere when:

• You handle regulated data (HIPAA, SOC 2, PCI) or need per-user attribution and audit trails — a shared secret provides no identity.
• You need MFA, session revocation, tenant isolation, or role-scoped permissions.
• The secret would be pasted into chat, tickets, or docs, or you need rotation without a deploy.
• The panel is customer-facing or revenue-critical.
• Your team can write a 30-line middleware, or Laravel's built-in signed URLs, basic auth, and IP allowlists already cover the need — in which case the dependency isn't earning its keep.

How to Pitch It (Stakeholders)

For executives: This is a low-cost curtain, not a lock. It puts a secret-key gate in front of the admin panel so we can ship internal tooling and client demos on the current timeline instead of waiting on the SSO workstream. Install is trivial, license is MIT, and cost is zero. The honest framing: it reduces casual exposure and search-engine/opportunistic access, but it is not a compliance control and does not identify users. We should present it as a dated stopgap with a named replacement milestone, not as our security story.

For engineering: It's a Filament middleware that requires a configured secret in the request before the panel resolves. Confirm three things before merge: the secret comes from env/config and never from a committed file, the secret is stripped from access logs and not echoed in referrer headers, and unauthorized requests return 404 rather than 403 where that distinction matters. Pin the version and review the source — it's small enough to read in one sitting, which is the main mitigation for the 38-star maintenance risk. Plan the exit: an auth middleware or panel-level guard that can be swapped in without reworking routes. Treat this as an explicit, documented exception with an owner and an expiry date, not a permanent layer.