Weave Code
Laravel Trustup Io Authentification Laravel Package
deegitalbe/laravel-trustup-io-authentification
Laravel integration for Trustup.io authentication. This package helps connect your app to Trustup.io's auth service, secure routes, and handle user identity with minimal setup, making it easier to add Trustup.io login to Laravel projects.
Connect your Laravel project to our centralized authentication service
Frequently asked questions about Laravel Trustup Io Authentification
- How do I install deegitalbe/laravel-trustup-io-authentification in a Laravel app?
- Install with Composer using composer require deegitalbe/laravel-trustup-io-authentification. Then configure the Trustup.io auth environment values, especially TRUSTUP_IO_AUTH_DOCKER_URL if you use a custom endpoint. Clear Laravel's config cache with php artisan config:clear and run your authentication flow in a non-production environment first. Confirm Guzzle 7.13+ in your dependency graph because the current patch targets that compatibility.
- What Laravel and PHP versions does this Trustup.io authentication package support?
- The package is built for Laravel/PHP applications and follows standard Composer and Laravel env/config conventions. The provided assessment explicitly calls out Guzzle 7.13+ compatibility for v4.0.1, but it does not list exact Laravel or PHP version constraints. Check the package's composer.json on GitHub for the authoritative Laravel, PHP, and Guzzle requirements before upgrading. If your app uses an older Laravel or Guzzle version, test the install in a branch first.
- How does TRUSTUP_IO_AUTH_DOCKER_URL work and is it required?
- It is the environment variable exposed by v4.0.1 for the Docker auth service URL used by the package. The patch adds a scheme to the default Docker auth service URL and lets you override it through TRUSTUP_IO_AUTH_DOCKER_URL. It is likely optional if the package default is valid for your deployment, but custom auth endpoints must be set correctly. Include http:// or https:// in custom values unless you have confirmed the package normalizes scheme-less URLs.
- Do I need to update Guzzle to use this package version?
- Version 4.0.1 is a narrow compatibility patch targeting Guzzle 7.13+. Confirm your application's Guzzle version and transitive constraints before running composer update. If your dependency graph already resolves Guzzle 7.13 or newer, the upgrade should be straightforward. If not, coordinate the Guzzle upgrade with your platform team and test Docker auth handshakes in staging.
- How do I secure Laravel routes with Trustup.io authentication?
- The package is intended to connect your Laravel app to Trustup.io's centralised auth service and handle user identity with minimal setup. Route protection is typically done through Laravel middleware and auth configuration, but the exact middleware names should be confirmed in the repository documentation. Install the package, configure the auth endpoint, and apply the documented middleware or guards to the routes you want to protect. Test both authenticated and unauthenticated requests before deploying.
- What should I check before deploying this package to production?
- Clear the Laravel config cache after setting environment values, especially if you changed TRUSTUP_IO_AUTH_DOCKER_URL. Validate Docker auth handshakes and login flows in a staging environment that mirrors production. Monitor auth error rates and logs after deploy because failure modes are likely auth or HTTP errors rather than application-wide outages. Keep a rollback pin to the previous package version in case auth errors appear.
- Does this package work with Docker auth flows or only auth.trustup.io login?
- The package description focuses on logging users into your Laravel application through Trustup.io's centralised authentication at auth.trustup.io. The v4.0.1 assessment specifically discusses a Docker auth service URL and Guzzle compatibility, so the patch affects that Docker auth URL path. Confirm in the repository whether the same configuration also governs other HTTP paths or only Docker auth. If your app uses both Trustup.io login and Docker auth, test both flows after upgrading.
- How should I test the Trustup.io authentication integration in Laravel?
- Run your normal Laravel test suite after installing or upgrading the package, then add or run integration tests that exercise the auth handshake against a non-production Trustup.io or Docker auth endpoint. Verify that environment values include a scheme and that config cache is cleared before tests. Check authenticated route access, unauthenticated redirects or errors, and user identity mapping. Do not rely only on unit tests because the failure modes here are often HTTP and configuration related.
- What are alternatives to deegitalbe/laravel-trustup-io-authentification?
- The closest alternative is integrating directly with Trustup.io's authentication API instead of using this Laravel wrapper, which gives more control but requires custom HTTP and identity handling. For general Laravel SSO you might evaluate Laravel Socialite or an OIDC/OAuth2 package, but those are not drop-in replacements for Trustup.io-specific authentication. If you already use Trustup.io, this package is the narrowest fit because it follows Laravel env/config conventions and targets the auth.trustup.io service. Compare maintenance ownership and Guzzle compatibility before choosing a custom integration.
- Is this package actively maintained and what is the upgrade risk?
- The assessment describes v4.0.1 as a low-risk patch-level compatibility release with routine Composer dependency maintenance. Maintenance effort is expected to be low, but you should keep TRUSTUP_IO_AUTH_DOCKER_URL documentation current and track Guzzle compatibility. Upgrade risk is mainly environment drift, stale config cache, and scheme-less custom URLs rather than architectural impact. Pin the previous version for rollback and review repository releases before future upgrades.
Weaver
How can I help you explore Laravel packages today?