Weave Code
Puzi Laravel Laravel Package
minvws/puzi-laravel
Laravel package for integrating MinVWS PUZI into your application. It provides the framework glue—configuration and Laravel-friendly service bindings—to use PUZI functionality with Laravel’s container and conventions, making it easier to add PUZI support to Dutch healthcare projects.
Laravel bundle for UZI authentication
Frequently asked questions about Puzi Laravel
- What is minvws/puzi-laravel used for?
- minvws/puzi-laravel is a Laravel package for integrating MinVWS PUZI into your application. It provides the framework glue, configuration, and Laravel-friendly service bindings needed to use PUZI functionality with Laravel's container and conventions. It is aimed at Dutch healthcare projects that need UZI authentication or certificate handling. The package does not replace domain knowledge of Dutch healthcare PKI and UZI certificates.
- How do I install minvws/puzi-laravel with Composer?
- Install it as a Composer dependency, typically with composer require minvws/puzi-laravel. Laravel package auto-discovery is expected to register the service provider and configuration. Publish the package configuration if the documentation asks for it, then set the certificate paths and other PUZI options for your environment. Run your application tests after installation to confirm the service bindings resolve.
- Which Laravel and PHP versions are supported by minvws/puzi-laravel?
- The supported PHP and Laravel versions are defined in the package composer.json and should be checked before upgrading. The assessment notes that compatibility depends on those constraints, so confirm them for your application's PHP and Laravel versions. If you are on an older Laravel release, verify whether the package still supports it or plan an upgrade path.
- Is the CA certificate parser class in minvws/puzi-laravel part of the public API?
- The v3.2.2 release moves CA certificate parsing into a dedicated class, which improves separation of concerns and testability. The assessment does not confirm that the parser class is public API, and the patch version suggests a drop-in upgrade from v3.2.1. You should check whether your code or custom extensions referenced the old parser class directly. If they did, verify the new class name and behavior before deploying.
- Are there breaking changes in minvws/puzi-laravel v3.2.2?
- v3.2.2 is a patch release, which by semver indicates backward compatibility. The main risk noted is unintended API impact from moving CA certificate parsing into a dedicated class, especially if consumers extended or referenced the old parser. Treat it as a low-risk patch from v3.2.1 but run your certificate and authentication tests. From v2.x or earlier, expect a major-version migration rather than a patch upgrade.
- How does minvws/puzi-laravel surface UZI certificate validation errors?
- The assessment does not document the exact error-handling API, so you should review the package source and documentation for thrown exceptions or validation result objects. Add monitoring around authentication and certificate-related paths so parsing exceptions and validation failures are visible. Log certificate parsing warnings and alert on repeated authentication failures. Use representative test UZI certificates and CA chains to confirm how errors appear in your application.
- Does minvws/puzi-laravel cache parsed certificates?
- Caching behavior is not confirmed in the provided context. Certificate parsing is typically lightweight, but the assessment recommends avoiding parsing certificates on every request and caching validated results where appropriate. Check the package configuration and source for any built-in cache support. If none exists, add application-level caching carefully and invalidate it on certificate rotation or expiry.
- What security policy and release cadence does minvws/puzi-laravel follow?
- The package is maintained by MinVWS, but the assessment notes that no prior assessment exists and the security posture is unverified. It also warns that ministry maintenance may mean a slower security release cadence. Establish a routine to review GitHub issues, security advisories, and ministry releases. Document your internal escalation path for UZI/PKI incidents.
- What test coverage exists for the CA certificate parser refactor in minvws/puzi-laravel v3.2.2?
- The assessment states that moving CA certificate parsing into a dedicated class improves testability but does not quantify test coverage. Before upgrading, run your own unit and integration tests for authentication and certificate parsing. Validate against representative UZI certificates and CA chains in a non-production branch. Check the repository for tests related to the parser and certificate validation.
- How do I migrate from minvws/puzi-laravel v2.x to v3.2.2?
- From v2.x or earlier, expect a major-version migration; review the upgrade guides and API changes before proceeding. For the final step to v3.2.2, update the Composer constraint in a non-production branch and run your application tests. Verify certificate parsing with representative UZI certificates and CA bundles, then deploy to staging and exercise authentication flows. Roll out to production with a rollback plan and monitor logs for certificate parsing warnings.
Weaver
How can I help you explore Laravel packages today?