- How do I install invisnik/laravel-steam-auth in a Laravel app?
- Install it with Composer using composer require invisnik/laravel-steam-auth. As a Laravel library it is expected to register its service provider through package auto-discovery, so no manual provider entry should be needed. After installing, publish any package configuration if the README instructs you to, then set your callback URL and API credentials.
- Does laravel-steam-auth support Laravel 9?
- Yes. The v4.4.0 changelog explicitly adds Laravel 9.0 support via PR #130. Because that shipped as a minor version bump, the intent appears to be broadening compatibility rather than introducing breaking changes. Confirm the exact illuminate/* and PHP constraints in the package composer.json before you upgrade.
- How do I configure the Steam login redirect and callback routes?
- Setup is intentionally minimal: you redirect the user to Steam's OpenID endpoint, then handle the callback that Steam returns to your app. The package exposes configuration, typically published into your config directory, covering the callback URL and API access. Check the README for the exact route names, config keys, and any middleware you need to apply.
- How do I retrieve a user's Steam ID and profile data after login?
- After the callback is validated, the package resolves the authenticated Steam ID and can fetch profile data through its configurable API. You then attach that Steam ID to your application's user record or session. Treat the returned profile data as external input and validate it before persisting anything.
- Does this package still work with Laravel 8?
- The v4.4.0 release is described as adding Laravel 9 support, not dropping Laravel 8, and it shipped as a minor version. That is a good sign for a wide compatibility window, but the authoritative answer is the composer.json constraint. Check whether the PHP floor was raised at the same time, since that would quietly affect Laravel 8 users.
- Is the package compatible with PHP 8 and Laravel 9 Symfony 6 dependencies?
- Laravel 9 requires PHP 8.0 or newer and pulls Symfony 6 components, so the package's illuminate/* and transitive constraints must permit that set. A minor release adding Laravel 9 support suggests the maintainer widened constraints rather than forking the code. Verify the resolved dependency tree on a test branch, particularly if you also maintain Laravel 8 services.
- How do I test Steam OpenID authentication in a Laravel application?
- Steam OpenID is an external redirect flow, so unit tests should fake or stub the package's HTTP calls and callback handling instead of contacting Steam. Exercise the callback path with a known Steam ID response and assert that your app links the correct user. Also cover the failure path where OpenID validation fails or the user cancels.
- What are the alternatives to laravel-steam-auth for Steam login?
- Alternatives include other Laravel Steam authentication packages and implementing Steam OpenID directly with Laravel's HTTP client. This package's value is the minimal setup: redirect, callback, and profile retrieval behind a configurable API. Compare maintenance activity, Laravel version support, and how much of the OpenID flow you want to own before choosing.
- Is invisnik/laravel-steam-auth actively maintained?
- The available evidence is limited to the v4.4.0 changelog adding Laravel 9 support, so maintenance cannot be fully judged from it. The fact that a community pull request was merged and released is a positive signal. Review recent commits, release cadence, and CI status on the repository before adopting it.
- Does installing this package require migrations or changes to my users table?
- This is an authentication package, not a user management package, so it should not require migrations or changes to your users table. You store the returned Steam ID in your own schema, for example a steam_id column or a linked accounts table. Confirm in the README whether any optional migration is published.