Saml2 Bridge Bundle Laravel Package

Product Decisions This Supports

• Enterprise SSO Integration: Enables seamless integration with SAML-based identity providers (e.g., Okta, Azure AD, OneLogin) for B2B/B2G clients requiring federated authentication.
• Compliance & Security: Supports Single Sign-On (SSO) and Single Logout (SLO) for compliance with regulations like GDPR, HIPAA, or FERPA where identity federation is mandatory.
• Roadmap for Multi-Factor Authentication (MFA): Foundation for future MFA integration via SAML extensions (e.g., binding user attributes to MFA flows).
• Build vs. Buy: Avoids reinventing SAML wheels; leverages simplesamlphp/saml2 (battle-tested) while abstracting Symfony-specific complexity.
• Use Cases:
  • Partner portals requiring SAML-based access.
  • Government/education sector integrations (e.g., InCommon, eduroam).
  • Internal tooling where legacy systems mandate SAML.

When to Consider This Package

• Adopt if:

  • Your stack is Symfony/Laravel (with Symfony components) and you need lightweight SAML IdP without heavyweight alternatives (e.g., Shibboleth).
  • You require basic SAML 2.0 (SSO/SLO) with HTTP-POST/Redirect bindings—no advanced features like attribute queries or encrypted assertions.
  • Your team lacks SAML expertise; the bundle abstracts low-level complexity.
  • You’re GPL-3.0 compatible (or can relicense proprietary extensions).

• Look elsewhere if:

  • You need Service Provider (SP) functionality (this is IdP-only).
  • You require SAML 2.1 or advanced features (e.g., Just-In-Time provisioning, attribute filtering).
  • Your project demands high customization (e.g., non-standard metadata formats); the bundle’s maturity is low (no active maintenance, minimal stars).
  • You’re in a closed-source project and GPL-3.0 is incompatible.
  • You need commercial support (this is open-source only).

How to Pitch It (Stakeholders)

For Executives:

"This bundle lets us integrate with SAML-based identity providers (like Okta or Azure AD) with minimal dev effort, enabling secure, federated access for partners/clients—critical for [compliance/partnership X]. It’s a lightweight, cost-effective alternative to custom builds or expensive third-party tools, with the added benefit of future-proofing our auth infrastructure for MFA and B2B use cases."

For Engineering:

*"We’re adding AdactiveSAS’s SAML2 Bridge Bundle to:

• Reduce dev time: Wraps simplesamlphp/saml2 (a trusted library) with Symfony-friendly abstractions.
• Support SSO/SLO: Covers HTTP-POST/Redirect bindings for basic SAML flows (no SP, but we can extend later).
• Risk: Low maturity (0 stars, no maintenance), but the underlying library is stable. We’ll need to:
  • Validate metadata generation for our use case.
  • Plan for potential forks if issues arise.
  • Document gaps (e.g., no SP support) upfront. Alternatives: Custom SAML (high effort) or commercial tools (high cost). This strikes a balance."*

Key Tradeoff: Speed vs. control—ideal for MVP or compliance-driven projects, but not for highly customized or mission-critical SAML deployments.