- How do I install laravel4-saml2 in a Laravel 4 application?
- Install it with Composer by requiring pitbulk/laravel4-saml2 in your Laravel 4 project, then register the package service provider in your app configuration. After that, publish or create the package configuration and set your SAML SP and IdP values. Composer handles the OneLogin toolkit dependency.
- How do I configure laravel4-saml2 as a SAML service provider?
- Configure the package wrapper with your service provider entity ID, assertion consumer service URL, and signing certificate or key, then add the identity provider SSO URL and certificate. The OneLogin toolkit performs the SAML request and response handling behind those settings. Make sure the ACS URL matches what is registered with your IdP.
- Can laravel4-saml2 act as a SAML identity provider as well as a service provider?
- The package overview describes it as a service provider integration based on the OneLogin toolkit, while the project blurb also mentions identity provider support. Review the available configuration and documentation to confirm whether IdP mode fits your use case. For production, verify the exact behavior in a test environment.
- Which Laravel versions are supported by laravel4-saml2?
- laravel4-saml2 targets Laravel 4 specifically, as its package name and integration indicate. It is not intended for Laravel 5 and later releases. For newer Laravel versions, look for a maintained SAML package built for that framework version.
- How does laravel4-saml2 relate to the OneLogin PHP SAML toolkit?
- It is a Laravel 4 integration wrapper around the OneLogin PHP SAML toolkit, exposing SAML 2.0 SSO configuration through Laravel. The toolkit handles protocol details while the package simplifies setup for your application. This makes it an alternative to heavier SAML stacks such as SimpleSAMLphp.
- Can I use laravel4-saml2 for production single sign-on?
- Yes, you can use it for production SSO if you correctly configure SP and IdP metadata, certificates, HTTPS, and logout flows and test them against your identity provider. Because it targets Laravel 4, which is end-of-life, you should also review security maintenance and dependency updates. Pin Composer versions and audit the OneLogin toolkit dependency.
- How can I test SAML SSO with laravel4-saml2 locally?
- Test with your IdP's sandbox metadata or a local test identity provider and point the ACS URL back to your Laravel 4 application. Use a local hostname that matches the registered SAML configuration and verify login, assertion validation, and logout. If HTTPS is required by your IdP, use a local TLS proxy or test domain.
- What are alternatives to laravel4-saml2 for SAML in Laravel?
- Alternatives include using the OneLogin PHP SAML toolkit directly, SimpleSAMLphp, or a maintained Laravel SAML package that matches your Laravel version. For new applications, choose a package with active maintenance and support for current Laravel releases. The right choice depends on whether you need SP-only or broader SAML and IdP support.
- Is laravel4-saml2 still maintained?
- The package targets Laravel 4, so its maintenance status should be checked on the GitHub repository before adopting it. Look for recent commits, issues, and compatibility notes with the OneLogin toolkit. For new projects on supported Laravel versions, prefer a maintained SAML integration.
- What SAML service provider metadata settings do I need to configure?
- You will typically need your SP entity ID, assertion consumer service URL, single logout URL, and signing certificate or private key, plus the IdP SSO URL and signing certificate. Set these through the package configuration wrapper so the OneLogin toolkit can build and validate SAML messages. Keep metadata aligned with what your identity provider has registered.