6.1.1

6.1.1

Changes to make the metadata more aligned with the SAML metadata specification.

• Add keywords to each idp entry in idps-metadata #825
• Empty displayname/description in idps-metadata #825
• md:Organization block missing in idp metadata and misses url #826

6.1.0

The metadata endpoints of EngineBlock have been under heavy maintenance in this release. Some highlights include the move of all generation logic to the new Symfony EngineBlock application. But maybe more important, EngineBlock no longer relies on entity information from the sso_provider_roles_eb5 table. All EngineBlock metadata is either loaded from ini config, or is hardcoded into the application. Because the Eb entities were purely an internal EB necessity you could now remove them by removing them from Manage and then execute a metadata push.

The unused metadata entities are the following:

• engine.{{ base_domain}./authentication/sp/metadata
• engine.{{ base_domain}//authentication/idp/metadata

Features

• Twig is used as template engine #759
• User friendly errors are displayed when metadata can not be created #770 (resolves issue #211)
• Metadata is now generated in the Symfony EngineBlock application #765 #771 #772 #773 #776 #783 #784 #785 #791
• The EngineBlock home screen was updated (slightly) #768 #769
• eduGAIN support was removed from the project #767
• Remove unused metadata entities and logic #811

Improvements

• Test coverage was a high priority (unit and functional tests are provided for every important feature) #766 #779 #780 #794 #795

Other chores

• Third party dependencies: Doctrine ORM, PHPUnit, Phake and Mockery have been updated #764 #777
• Update ChromeDriver to match Chrome version #793
• The dev and test cache locations have been moved to a location outside the project directory #780
• Technical documentation was added to the wiki.

6.0.2

Bugfix

• Fix namespace after cherry picked bugfix #820

6.0.1

This release is a bugfix release to prevent the 5.13 release from becoming broken after migrations running the migrations in the 5.13 release.
The migrations dropped columns which still were in use by 5.13 and is needed to support the rolling updates.

Bugfix

• Remove migration to support 5.13 #817
• Prevent invalid assertion when stepup LoA is set #819

6.0.0

In this release, PHP 5.6 support was dropped in favour of PHP 7.2. We are not migrating to the latest PHP version for some reasons. Chief amongst which is that PHP 7.2 was best compatible with the current EngineBlock code base.
An upgrade to 7.3 or even 7.4 would force us to upgrade many third party dependencies at the same time, making this release much bigger.

For installation instructions, see the UPGRADING.md entry for this version.

The following changes where introduced in this release:

Improvements

• PHP 7.2 compatibility changes #713
• Prevent WAYF button from floating left #760
• Verify received LoA in StepUp ACS processing step #800
• Added IDPentityID to the Attribute Aggregation request #799 (thanks @ohastra)

Bugfix

• Get termsOfServiceUrl from coins, not SP metadata entity #756

Other chores

• Cleanup old coin columns #755
• Update Composer settings for improved PHP 7.2 support #763
• Update testing tools (PHPUnit, Mockery & Phake) #777
• Fixed typos #790 #809

Security

• Upgrade xmlseclibs to version 3.0.4 #802
• Upgrade symfony/mime to v4.3.8 #805
• Bump handlebars to version 4.3.1 #761
• Upgrade handlebars to 4.5.1 #805

5.13.3

This is a security release that will harden the application against CVE 2019-3465

• Implement countermeasures against CVE 2019-3465 #803/#802

5.13.2

A missing feature was implemented

• Add missing trusted proxy to stepup callout

5.13.1

Hotfix use of coins in consent template

5.13.0

Add stepup authentication to EB to be able to reap the benefits of the SFO functionality of the strong authentication stack.

• Add stepup authentication #754 (this is a composition of several PR's)
• For more specific details see the SFO pull requests between #721 and #754

5.12.0

We've changed the way how coin entity properties are stored in the database. As of now, they will be stored in a serialized manner, in a single column. This greatly simplifies adding or removing coins in the future, as this no longer requires database schema changes.

Please consult the UPGRADING.md to see how to upgrade to this version without a hassle.

• Store coin properties in a single column #752