- How do I install ziffmedia/laravel-onelogin in a Laravel application?
- Install it with Composer using composer require ziffmedia/laravel-onelogin, then publish the package configuration file. Populate the OneLogin identity provider settings such as entity ID, SSO URL, and x509 signing certificate. After that, register the package routes and wire the authentication guard into your app.
- Does ziffmedia/laravel-onelogin support Laravel 11 and Laravel 12?
- Laravel 11 and 12 support is not verified, and the last release was in September 2023. The package's illuminate/* constraints may block newer framework upgrades. Check the compatibility matrix and open pull requests before committing, and be prepared to fork or vendor the package if needed.
- How do I configure OneLogin IdP metadata for this Laravel package?
- Publish the package config file and fill in the OneLogin entity ID, SSO URL, and x509 signing certificate from your OneLogin tenant. Register the login redirect, ACS callback, and metadata endpoints provided by the package. A sandbox spike with an existing OneLogin tenant is usually the fastest way to validate the configuration.
- Does this package handle just-in-time user provisioning and attribute-to-role mapping?
- The package handles SAML responses and user provisioning, but you should verify how much attribute mapping is configurable. If attribute names are hardcoded to OneLogin claim names, portability to Entra ID or Okta is reduced. Plan to test JIT provisioning and role mapping against your actual IdP assertions.
- Is single logout (SLO) supported by ziffmedia/laravel-onelogin?
- The package describes login and logout flows, but full single logout semantics need verification and testing. Partial SLO is a common silent failure in SAML integrations. Test logout behavior across both the IdP and your Laravel session before relying on it in production.
- What SAML toolkit does this package depend on, and are there security concerns?
- The package is a thin Laravel service-provider wrapper around a SAML 2.0 toolkit, so it inherits that dependency's security posture. SAML libraries are a known CVE surface for XML signature wrapping, XXE, and assertion parsing issues. Run an advisory scan on the pinned toolkit version before adopting it.
- Can ziffmedia/laravel-onelogin support multiple identity providers or multi-tenant setups?
- It appears to be designed for a single OneLogin identity provider connection rather than multi-tenant or multi-IdP use. If you need per-tenant IdP configuration, verify whether the config and routes can be extended or whether you need a different package. Treat multi-tenancy as an open question during evaluation.
- Is ziffmedia/laravel-onelogin actively maintained and safe for production?
- Adoption signals are limited: roughly 10 stars, a single-vendor release history, and no disclosed security contact or SLA. The package is best treated as evaluate, vendor, and own rather than community infrastructure. It is a conditional fit for a bounded internal app where your team accepts ownership.
- How long does a Laravel OneLogin SSO integration take, and how do I migrate from local auth?
- With an existing OneLogin tenant, a sandbox spike can close in about one to three engineering days. A production-grade rollout with JIT provisioning, role mapping, and dual-auth transition should budget one to two additional weeks. Keep local auth active behind a feature flag and preserve a break-glass account during migration.
- What are alternatives to ziffmedia/laravel-onelogin for Laravel SAML SSO?
- Consider actively maintained Laravel SAML2 packages, Laravel Socialite-based SAML providers, or direct integration with a current SAML toolkit. Evaluate alternatives on Laravel 11 and 12 support, CVE posture, test coverage for signature validation failures, and multi-IdP flexibility. The right choice depends on whether you need a simple OneLogin bridge or a platform-wide authentication standard.