- What is tobymaxham/zhylon-auth used for?
- It is a Laravel Socialite provider that adds Zhylon OAuth2 authentication to Laravel applications. You use it to let users sign in with their Zhylon account instead of building the OAuth2 handshake yourself. It is not a complete authentication scaffold; your app still handles user persistence, sessions, and authorization.
- How do I install tobymaxham/zhylon-auth in a Laravel app?
- Install it with Composer using composer require tobymaxham/zhylon-auth. Laravel package discovery should register the service provider automatically; if not, add the provider to your bootstrap/providers.php or config/app.php as appropriate for your Laravel version. Then configure your Zhylon OAuth client credentials and redirect URI before using the driver.
- Does this package work with Laravel Socialite?
- Yes, the package is described as a Zhylon OAuth2 provider for Laravel Socialite. It extends Socialite so you can call Socialite::driver('zhylon')->redirect() and handle the callback with Socialite::driver('zhylon')->user(). You still need laravel/socialite installed and your Zhylon OAuth application configured.
- How do I configure Zhylon OAuth credentials for Laravel?
- You typically add a zhylon entry with client_id, client_secret, and redirect URI to config/services.php, following standard Socialite conventions. Confirm the exact key names and any package-specific config file in the README, because the provider may expect a dedicated config block. The redirect URI must exactly match the callback URL registered in your Zhylon OAuth application.
- Which Laravel versions does tobymaxham/zhylon-auth support?
- Check the package composer.json for its illuminate/socialite and PHP version constraints before installing. The provider must resolve against your Laravel and Socialite versions, and older packages may not support the newest Laravel release. If Composer reports a conflict, avoid forcing the install unless you have reviewed and tested the code.
- How do I add a Zhylon login button or route in Laravel?
- Create a route such as GET /auth/zhylon that returns Socialite::driver('zhylon')->redirect(). Add a callback route that calls Socialite::driver('zhylon')->user(), then find or create your local user and call Auth::login(). Link your login button to the redirect route and make sure the callback URL matches your Zhylon configuration.
- Can I use this package for registration and access control, or only OAuth login?
- The package is primarily a Zhylon OAuth2 Socialite provider, so its core responsibility is the OAuth redirect and user retrieval. The broader description mentions configurable guards and user flows, but you should verify in the README and source what is actually bundled. In most Laravel apps you will still implement registration, roles, and access control in your own user model, middleware, and policies.
- How do I test Zhylon OAuth authentication in a Laravel application?
- Test your redirect route for the correct Zhylon authorization URL and test the callback route with a mocked Socialite user. You can mock the Socialite driver or fake the underlying HTTP responses so tests do not call Zhylon. Assert that your app creates or updates the local user and logs them in correctly, including failure cases such as denied consent or invalid state.
- Is tobymaxham/zhylon-auth actively maintained and safe for production?
- Community adoption is described as minimal, so review the GitHub repository for recent commits, releases, and open issues before relying on it in production. Check Packagist download statistics and confirm the package supports your Laravel and Socialite versions. Pin a specific version, review the provider code, and have a fallback plan such as a custom Socialite driver if maintenance stops.
- What are alternatives to tobymaxham/zhylon-auth for Laravel OAuth2 login?
- You can write a custom Laravel Socialite driver for Zhylon if the package does not fit your needs. The SocialiteProviders community collection may offer generic OAuth2 providers, and Laravel Fortify or Jetstream can handle broader authentication scaffolding. For non-Zhylon providers, official Socialite drivers are usually the safest choice.