- How do I install and configure esplora/auto-login in a Laravel app?
- Install esplora/auto-login with Composer using composer require esplora/auto-login, then publish the package configuration if your integration needs to customize routes or token behavior. The package is designed for simple route and middleware integration, so review the published config and registered routes before enabling it in production. Confirm the exact publish command in the package documentation or changelog for version 1.0.0.
- Does esplora/auto-login work with Laravel's existing guards and user providers?
- Yes. The package is built to authenticate users through Laravel's native guard system and works with your existing guards and user providers rather than requiring a separate authentication stack. You should still verify guard resolution in your application, especially if you use multiple guards or custom providers.
- How do I generate a secure auto-login URL for a user?
- Use the package's URL generation API to create a signed auto-login URL for any authenticatable model, such as your User model. The generated URL is tied to that account and is validated when the request hits your auto-login route. Refer to the package source or changelog for the exact method names and available options in version 1.0.0.
- Can I make auto-login links expire and be single-use?
- Yes. Esplora Auto Login supports configurable token lifetime and single-use enforcement, so you can limit how long a link remains valid and prevent replay after first use. Review the published config to set expiry and single-use behavior to match your security requirements.
- What happens when an auto-login link is invalid or expired?
- Invalid or expired auto-login links are handled with sensible redirects instead of authenticating the user. You should review and customize the redirect targets in the package configuration so failed links land on an appropriate login, error, or support page.
- Is esplora/auto-login suitable for magic-link email login?
- Yes. The package is intended for passwordless flows such as email magic links, invitation links, and one-click access from external systems. It generates tokenized login URLs and authenticates the user through Laravel's guard system, so it fits naturally alongside a standard Laravel session-based login flow.
- Which Laravel and PHP versions does esplora/auto-login support?
- The package's README excerpt does not advertise specific Laravel or PHP version constraints, so check its composer.json requirements before planning an upgrade or integration. Version 1.0.0 is the first stable tag, but you should confirm compatibility with your pinned Laravel and PHP versions directly from the repository.
- Is esplora/auto-login safe to use in production?
- Treat auto-login as a security-sensitive authentication path and review token generation, entropy, expiry, single-use enforcement, rate limiting, and revocation before production use. The package provides configurable lifetime and single-use behavior, but the overview does not advertise a formal security policy, so establish an internal review process. For production, stage the rollout behind a feature flag and monitor authentication events.
- Does esplora/auto-login support multi-guard or multi-tenant Laravel apps?
- The package is designed to work with existing Laravel guards and user providers, but multi-guard and multi-tenant setups require verification of how the guard is resolved for each login link. Test admin and user guard scenarios in a sandbox before relying on it in a multi-guard application.
- How should I test auto-login flows in a Laravel application?
- Test auto-login flows by generating links for known users, asserting the redirect and authenticated guard, and covering expired, invalid, and already-used tokens. Use Laravel's HTTP testing tools to exercise the route and middleware integration end-to-end. Because authentication is security-sensitive, also add tests for single-use enforcement and redirect behavior on failure.