Weave Code
Saml Sp Bundle Laravel Package
aerialship/saml-sp-bundle
Symfony2 bundle providing a SAML 2.0 Service Provider: authenticate against one or more IdPs with SSO (AuthnRequest), Single Logout, federation metadata, discovery service, and HTTP-POST/Redirect bindings. Legacy; newer version exists.
SAML 2.0 Symfony SP Bundle - new version available at
Frequently asked questions about Saml Sp Bundle
- Is this package compatible with Laravel? I only see Symfony2 support.
- No, this bundle is **exclusively for Symfony2** and won’t work in Laravel. For Laravel SAML integration, consider alternatives like **onelogin/php-saml** or **janrain/phpsaml** directly, or a Symfony-to-Laravel bridge if absolutely necessary.
- What Laravel alternatives exist for SAML 2.0 Service Provider (SP) authentication?
- For Laravel, use **onelogin/php-saml** (standalone) or packages like **spomky-labs/saml** (built on top of it). If you need a Laravel-specific bundle, check **laravel-saml** or **saml2-laravel** on Packagist, though they may lack full SAML 2.0 feature parity.
- Which Symfony versions does this bundle support? Can I use it with Symfony 5+?
- This bundle **only supports Symfony 2.3–2.7**. It is **not compatible** with Symfony 3+, 4+, or 5+. For newer Symfony versions, use **lightSAML/sp-bundle** (successor) or migrate to a modern SAML library like **onelogin/php-saml** with custom integration.
- How do I configure multiple Identity Providers (IdPs) in this bundle?
- Define each IdP in `config.yml` under `saml_sp.idp` with unique keys (e.g., `idp_okta`, `idp_azure`). Use the `discovery_service` to let users select their IdP via a dropdown. Ensure each IdP’s metadata XML is properly formatted and accessible via HTTP or local file.
- Does this bundle support SAML attribute mapping to Laravel user models?
- No—this is a **Symfony2-only** bundle. For Laravel, you’d need to manually map SAML attributes (e.g., `email`, `firstName`) to your user model using the underlying **onelogin/php-saml** library or a Laravel-compatible SAML package like **spomky-labs/saml**.
- What are the risks of using this outdated bundle in production?
- The bundle relies on **onelogin/php-saml v2.x (last updated 2016)**, which lacks PHP 7.4+ and Symfony 3+ support. Risks include **security vulnerabilities**, **compatibility issues**, and **no future updates**. For production, prioritize **lightSAML/sp-bundle** or a maintained Laravel SAML package.
- How do I test SAML authentication flows locally before deploying to production?
- Use **test IdPs** like Okta’s sandbox, SimpleSAMLphp, or **onelogin’s test IdP**. Configure the bundle to point to these IdPs, then simulate SSO/SLO flows. Validate error handling (e.g., expired tokens, invalid metadata) by manually triggering failures in your IdP’s debug console.
- Can I integrate this bundle with Laravel’s authentication system via API?
- No—this bundle is **Symfony2-specific**. For Laravel, you’d need to expose SAML auth as a **microservice** (e.g., a Symfony2 app behind an API gateway) or use a **Laravel-compatible SAML library** like **spomky-labs/saml** to handle auth and forward tokens to Laravel via sessions or JWT.
- What PHP versions are supported, and will it work with PHP 8.x?
- This bundle requires **PHP 5.3.3+**, but **PHP 7.4+ may break compatibility** due to deprecated functions in **onelogin/php-saml v2.x**. For PHP 8.x, use **lightSAML/sp-bundle** or a modern SAML library. Test thoroughly if stuck with PHP 7.x.
- How do I handle SAML Single Logout (SLO) in this bundle, and does it work with all IdPs?
- Configure `slo_enabled: true` in your bundle settings and ensure your IdP supports SLO. The bundle uses **HTTP-Redirect** for SLO by default. Test with your IdP’s metadata to confirm compatibility—some IdPs (e.g., Azure AD) may require additional configuration like `NameID` format alignment.
Weaver
How can I help you explore Laravel packages today?