Weave Code
Laravel Config Sso Laravel Package
cleaniquecoders/laravel-config-sso
Laravel Config SSO centralizes single sign-on configuration for Laravel apps, making it easier to manage SSO settings, providers, and environment-specific options from one place—ideal for teams standardizing authentication across multiple applications.
laravel-config-sso is a Laravel package that brings Single Sign-On (SSO) integration into your application through a clean, configuration-driven approach. Rather than hardcoding authentication logic, you define identity providers, credentials, and callback settings in Laravel config files—keeping SSO setup readable and easy to adjust per environment.
- Config-first setup for SSO providers and endpoints
- Environment-aware credentials via
.env - Publishable config file for quick customization
- Support for multiple identity providers
- Fits naturally into Laravel's existing auth/guard flow
Frequently asked questions about Laravel Config Sso
- How do I install cleaniquecoders/laravel-config-sso in a Laravel app?
- Install it with Composer using composer require cleaniquecoders/laravel-config-sso, then publish the package config file and confirm the service provider is registered (Laravel package auto-discovery normally handles this). The admin screen is exposed at /admin/settings/sso and is rendered by a Livewire component using Flux components. No migrations or data-model obligations are implied by the release notes, so setup is essentially config publishing plus route exposure. Check the published config for the provider, credential, and route keys you need to declare.
- Which Laravel, PHP, Livewire, and Flux versions does laravel-config-sso support?
- The package targets Laravel 12 and 13, as stated in its description. The exact PHP, Livewire, and Flux version constraints live in its composer.json, so run composer show cleaniquecoders/laravel-config-sso or check Packagist before committing. Because the admin UI is coupled to Flux component and icon naming, a Flux major upgrade is the most likely source of compatibility drift. Pin your Livewire and Flux majors deliberately rather than relying on the widest available constraint.
- Does laravel-config-sso require Flux Pro or will Flux Free work?
- The package's settings screen is built from Flux components and Heroicons, and Flux is a commercial Livewire UI kit, so licensing is a real procurement question rather than just a Composer line. The release notes do not state whether the components used are available in the free tier or require a paid license. Verify the specific Flux components rendered by the SSO screen against your license before adopting it. If you are not already a Flux shop, adopting it for one settings screen is a disproportionate dependency.
- Are SSO client secrets stored encrypted at rest in laravel-config-sso?
- The release notes do not specify whether identity provider client secrets and certificates are encrypted in the database or read from config and env. Because the package is described as database-backed SSO provider management, this is the first thing to confirm in the source before using it in production. As a safer pattern, treat the package as operator convenience layered over an env or config driven setup rather than the sole source of SSO truth. Keep secrets in env or an encrypted store and restrict who can reach the admin screen.
- What middleware or gate protects /admin/settings/sso by default?
- Default route authorization for the SSO settings screen is not documented in the release notes and is listed as an open security question. SSO configuration is security-sensitive, so verify what middleware the package registers before exposing the route. Add your own auth and authorization middleware or gate around /admin/settings/sso, and confirm whether that protection is opt-in or opt-out. Also check whether configuration changes are audited, since an admin UI widens the blast radius compared with file-based config.
- Does laravel-config-sso support multiple identity providers or multi-tenancy?
- The package is described as configuration-driven SSO provider management, which suggests multiple providers can be declared in config, but multi-IdP and multi-tenant behavior is not confirmed in the release notes. The safest approach is to model one provider first, verify the credential and route keys work end to end, then test a second provider before relying on it for tenants. If per-tenant routing or credential isolation is a requirement, raise it with the maintainer before adopting.
- Can I use laravel-config-sso in a Blade and Tailwind app without Livewire or Flux?
- It is a poor fit for Blade and Tailwind-only applications. The admin screen is a Livewire component built from Flux components, so adopting it means adding Livewire, Flux, and Heroicons semantics to your stack for a single settings page. The underlying value, declaring SSO providers and routes in config, can be reproduced with Socialite and a plain config file. Defer this package unless your app already runs Livewire and Flux.
- Why do HTTP tests not catch broken Flux icons in laravel-config-sso?
- Flux renders icons as no-ops in the test harness, so a missing component name like icon.ellipsis can hard-fail the admin route at render time while HTTP tests still pass. The package added FluxIconTest in 1.0.2, but that is a static string guard scoped to icon names and only closes that specific instance, not the whole class of component drift. Add a rendered-route smoke test, such as a browser test or snapshot, if you want coverage of the next non-icon render failure. This matters most right after a Flux major upgrade.
- Why does /admin/settings/sso return a 500 error when running composer serve locally?
- Contributors have hit a boot failure caused by a stale Testbench cache, which makes every package route return a 500 under composer serve. It is a dev-environment issue rather than a production one, but it can make a first local run look like a broken package. Clear the Testbench cache and republish the workbench assets, including the compiled stylesheet, before evaluating. If the screen still fails, check the installed Flux major against the icon names used by the component.
- Is laravel-config-sso actively maintained and is its 1.0.x API semver-stable?
- The package is on a 1.0.x line with recent patch releases covering icon fixes, workbench tooling, a static regression test, and documentation, which are reasonable maintenance signals. However, 1.0.1 shipped a route-breaking UI regression, so quality is mixed at this maturity level. Whether the public surface of config keys, routes, and component names is committed to semver is not stated, and upstream support commitments are unclear. Treat it as effectively self-supported and pin the version in composer.json.
Weaver
How can I help you explore Laravel packages today?