This release bumps the minimum required PHP-version to 8.5 and migrates to the new PHP DOM-API that was introduced in PHP 8.4
Fixed CVE-2025-66475
Following up on v5 this is another intermediate step that changes the interface. A major change here is that instead of passing a 'string' to a method and validate that the string is a valid URI, we now pass an AnyURIValue object, drastically reducing the overhead of validating strings multiple times.
Appropriate to use for people who need to generate/parse SAML 2.0 messages/metadata, or use bindings. Still no full replacement for the old v4. We plan to release a full replacement for v4 in v6.1 where we add ServiceProvider/IdentityProvider where you pass all your configuration and metadata and then those classes will do all the heavy lifting to process requests/responses according to the SAML2 specifications.
Until we release a full replacement, we will keep supporting and patching v4
Version 5.0 of this library completely rewrites the library to modern standards. It is a necessary intermediate step for us to migrate away from the old v4, but it is in no way a replacement. You can still use it if your concern is just generating/parsing SAML 2.0 messages/metadata
Fixes CVE-2025-27773
Fix regression (missing use statement) introduced in 4.6.9.
Bugfix
Fix an invalid assertion, leading to an InvalidArgumentException when trying to set the AssertionConsumerServiceIndex on an AuthnRequest
Fix incorrect use of Issuer-class
Fix a mistake in the bugfix for #229
Fixes a bug in HTTPArtifact::receive (#229)
This is a bugfix release of the SAML2 library, fixing a critical security issue (SSPSA 201911-01).
This is a bugfix release of the SAML2 library, fixing a critical security issue (SSPSA 201911-01).
This is a bugfix release of the SAML2 library, fixing a critical security issue (SSPSA 201911-01).
This is a stable release of the SAML2 library.
The most significant changes are:
If you are a developer using this library as part of your application, make sure you read the Upgrade Notes
This is a bugfix release: v3.4.0 was accidentally based on master instead of the 3.x branch
SPProvidedID in NameID fromArray().mdui:Logo elements with data: URLs.Change the default signature algorithm from RSA-SHA1 to RSA-SHA256.
Please note that this change does not remove support for RSA-SHA1. However, when passing a XMLSecurityKey to verify a signature, that key must be created with the RSA-SHA256 algorithm.
Please note that this is the last 2.x release.
How can I help you explore Laravel packages today?