Oauth2 Uco Bundle Laravel Package

Product Decisions This Supports

• Single Sign-On (SSO) for Education Institutions: Enables seamless authentication for students, faculty, and staff using the University of Córdoba’s OP (OpenID Provider), reducing friction in academic platforms (LMS, portals, or admin tools).
• Compliance with Institutional Identity Standards: Aligns with regional or university-specific authentication requirements, avoiding custom OAuth2 integration efforts.
• Symfony Ecosystem Integration: Leverages Symfony’s security framework to embed SSO without reinventing authentication logic, accelerating development for higher-ed applications.
• Roadmap for Scalable Identity Solutions: Justifies investing in a maintainable, open-source bundle over proprietary alternatives, especially if the University of Córdoba’s OP is a strategic partner.
• Build vs. Buy: Avoids building a custom OAuth2 client for niche use cases (e.g., university-specific SSO) while maintaining flexibility for future protocol updates.

When to Consider This Package

• Target Audience: Only relevant if your product serves the University of Córdoba or similar institutions using its OP. For broader markets (e.g., generic OAuth2/OIDC), alternatives like league/oauth2-client or knpuniversity/oauth2-client-bundle are more versatile.
• Symfony Dependency: Requires a Symfony 5.4+/6.x/7.x project. Non-Symfony PHP apps (e.g., Laravel, plain PHP) need other solutions.
• License Constraints: AGPL-3.0 may conflict with proprietary software; evaluate compliance risks if bundling in closed-source products.
• Low Adoption: No stars/issues suggest unproven stability. Assess maintenance commitment (e.g., is aulasoftwarelibre active?).
• Alternatives Exist: If the University of Córdoba’s OP supports standard OIDC, generic bundles (e.g., gluu/federation) may suffice without vendor lock-in.

How to Pitch It (Stakeholders)

For Executives: "This bundle lets us integrate with the University of Córdoba’s SSO in weeks—not months—by reusing their open-source authentication framework. It cuts development costs, ensures compliance with their identity standards, and future-proofs our platform for academic partnerships. The AGPL license aligns with our open-education mission, and the Symfony integration keeps our tech stack lean."

For Engineering: *"We’re adopting this to avoid building a custom OAuth2 client for the University of Córdoba’s OP. It’s a lightweight Symfony bundle that handles:

• Token exchange with their provider (via oauth2-uco).
• User provisioning (Doctrine + Symfony Security).
• Session management (Messenger for async tasks). Tradeoff: AGPL license requires careful review, but the bundle abstracts 80% of the SSO boilerplate. If their OP changes, we can fork or negotiate support."*