Security release

Update onelogin/php-saml version requirement to 4.3.1 because of CVE-2025-66475 and robrichards/xmlseclibs CVE-2025-66475

All changes
4.0.4...4.0.5

Bugfix release

• [BUGFIX] do not set databaseDefaults without a value since this stops the overriding process of custom settings for this area

All changes
4.0.3...4.0.4

Maintenance release

• [TASK] check, if site configuration exists. Thanks to Georg Ringer!

All changes
4.0.1...4.0.2

Feature release

• [FEATURE] allow baseVariants in configuration. Thanks to Bruno86!

All changes
4.0.0...4.0.1

TYPO3 v13 compatibility

Migration from v3 to v4

• Activation of backend login is done in the extension configuration, which can be found
  in the TYPO3 backend in Settings -> Extension Configuration -> md_saml. Please set
  checkbox according to your needs!
• Remove the Typoscript constants of ext:md_saml from your configuration.
• Include the Site Set MdSaml base configuration (ext:md_saml) in the Site Configuration
  of your website.
• Add custom Site Set in your site package as shown below:

The following example shows, how to modify the default configuration of ext:md_saml:

EXT:my_extension/Configuration/Sets/MySet/config.yaml:

name: my_extension/md_saml
label: MdSaml config for my website
dependencies:
  - mediadreams/md_saml

EXT:my_extension/Configuration/Sets/MySet/settings.yaml:

md_saml:
  mdsamlSpBaseUrl: 'https://%env(BASE_DOMAIN)%'

  be_users:
    databaseDefaults:
      usergroup: 3
      lang: 'de'

  fe_users:
    saml:
      sp:
        entityId: '/login/?loginProvider=1648123062&mdsamlmetadata'
        assertionConsumerService:
          url: '/login/?loginProvider=1648123062&login-provider=md_saml&login_status=login&acs&logintype=login'

  saml:
    sp:
      x509cert: '%env(SAML_SP_X509CERT)%'
      privateKey: '%env(SAML_SP_PRIVATE_KEY)%'

    idp:
      entityId: 'https://auth.myprovider.de/adfs/services/trust'
      singleSignOnService:
        url: 'https://auth.myprovider.de/adfs/ls/'

      singleLogoutService:
        url: 'https://auth.myprovider.de/adfs/ls/'

      x509cert: '%env(SAML_IDP_X509CERT)%'

As you can see, you can use environment variables in your configuration in order
to configure different setups.

ATTENTION
Somehow, it is not possible to use environment variables in site sets at the moment. So if you want to use env vars, do it in the general site configuration in <project-root>/config/sites/<identifier>/config.yaml. Add following at the bottom of the config file:

settings:
  md_saml:
    mdsamlSpBaseUrl: '%env(SAML_BASE_DOMAIN)%'

General information on site sets can be found
here.

All code changes

3.0.7...4.0.0