Weave Code
Admin Auth Laravel Package
brackets/admin-auth
A Laravel package for adding a dedicated admin authentication layer to your app. It provides an admin guard, login and logout flows, and middleware to protect admin routes, with configurable settings for integrating admin access into existing Laravel projects.
Authentication into Admin UI interface.
Frequently asked questions about Admin Auth
- What is brackets/admin-auth used for in a Laravel app?
- brackets/admin-auth is a Laravel package that adds a dedicated authentication layer for an admin UI, providing an admin guard, login and logout flows, and middleware you can attach to admin routes. It is designed to sit alongside the Brackets admin stack rather than replace your application's core identity system. Most teams use it to give admin users a separate session and access boundary from regular application users.
- How do I install and configure brackets/admin-auth in Laravel?
- Install it with Composer, then register the service provider and publish any configuration the package ships, following the repository README for exact commands and paths. Because it belongs to the Brackets ecosystem, confirm that your Laravel version, PHP version, and admin-ui version line up before committing. Check whether it publishes migrations or config files, and pin the exact version you install.
- Which Laravel and PHP versions does brackets/admin-auth support?
- The repository README and composer.json are the authoritative source, and the technical evaluation notes a 2023 release, so very recent Laravel majors may not be covered. Compare the Composer constraints against your Laravel and PHP versions before installing. If your app runs a newer Laravel release, run a proof of concept rather than assuming compatibility.
- Do I need brackets/admin-ui to use brackets/admin-auth?
- This package is an authentication interface for brackets/admin-ui, so it fits best as an admin-panel companion inside an existing Brackets admin stack. Integration feasibility drops sharply for greenfield or non-Brackets applications, where it should be treated as an isolated adapter at most. Do not move core auth, SSO, or enterprise IAM onto it in a non-Brackets app.
- How does the admin guard and route middleware work?
- The package provides an admin guard plus middleware that you place on admin route groups so unauthenticated admin requests are sent to the admin login flow. You should review the guard and session configuration against your existing user providers to avoid collisions between the admin and web guards. Confirm the exact middleware alias and guard name in the published config before wiring up routes.
- Does brackets/admin-auth support password reset, remember me, or MFA?
- Because the package is primarily an authentication interface for the Brackets admin UI, whether password reset, remember me, or MFA are included depends on what the package and admin UI actually implement. Treat these as verification items in a proof of concept rather than assumptions. If you require MFA or enterprise IAM, keep that in your core auth layer.
- Is brackets/admin-auth safe to use in production?
- Authentication is a high-blast-radius surface, and this package has low adoption signals, so validate session handling, guard behavior, access control, and admin lockout scenarios before going live. Pin the version, integrate it behind an internal adapter or feature flag, and canary with a limited admin cohort. Document rollback steps and assign an internal owner before wider rollout.
- How should I test brackets/admin-auth before rolling it out?
- Run a time-boxed proof of concept in a disposable, non-production environment with the package pinned to its current release. Exercise login, logout, password reset, session expiry, guard isolation, and access-control failure paths across your supported database and session drivers. Record the results and keep a known-good version to roll back to if anything behaves unexpectedly.
- Is brackets/admin-auth actively maintained and widely used?
- Adoption signals are low, with roughly seven stars and no dependents, and visible release activity is limited, so assume community-only support with no SLA and no guaranteed security patch cadence. Pin the version, watch the upstream repository, and budget for forking or replacing the package if it stalls. Assign an internal owner and document its configuration and auth flows so knowledge is not held by one engineer.
- What are the alternatives to brackets/admin-auth?
- Alternatives include using Laravel's built-in guards with your own admin middleware, first-party starters such as Breeze or Jetstream with a separate admin guard, or admin panel packages that bundle their own authentication. The right choice depends on whether you are already committed to the Brackets admin UI ecosystem. For general-purpose authentication, standard Laravel guards remain the safer default.
Weaver
How can I help you explore Laravel packages today?