Skip to main content
Version: Next

Upgrade

Upgrade to 2026.3.7​

OAuth2 state Is Now Validated by the Authenticator (Security)​

OpenIdConnectAuthenticator::authenticate() now verifies the OAuth2 state before it redeems the authorization code (GHSA-3c44-2cx5-j5rr, login CSRF). Previously the state was only checked on the /auth/endpoint callback, which does not protect the Studio login route (/auth/login) when it is requested directly.

  • The state stored in the session (OpenIdConnectAuthenticator::SESSION_KEY_STATE) must be present and match the state query parameter of the request (compared with hash_equals()). Otherwise authentication fails with an AuthenticationException (Invalid OAuth2 state) and the authorization code is never redeemed.
  • The stored state is removed from the session by authenticate(), whether validation succeeds or fails, so it cannot be replayed. A request with a wrong or missing state therefore also invalidates a login that is currently in progress in the same session. The user has to start the login again.
  • The method signature and return type are unchanged. The standard login flow (/auth/endpoint redirecting to /auth/login) already carries a matching state and needs no changes.

Note: Custom code that reaches the login route without going through the bundle's /auth/endpoint step is affected: custom endpoint implementations, classes extending or decorating OpenIdConnectAuthenticator and calling authenticate(), and scripted or end-to-end logins that send a code straight to the login route. They must store the state in the OIDC session bag (SESSION_KEY_STATE) when starting the authorization and pass the same value back as the state query parameter. This check cannot be disabled, as it is the fix for the vulnerability.

Upgrade to 2026.2.3​

Frontend Build Ships as a Packaged Archive​

The compiled Studio frontend is no longer committed as an expanded src/Resources/public/studio/build/ directory. It now ships as a single archive (build-dist/build-<id>.zip) that is extracted into src/Resources/public/studio/build/ automatically during cache warmup.

pimcore/studio-ui-bundle ^2026.2.1 is now required, as it provides the archive extraction.

Note: Read-only filesystem deployments must run bin/console cache:warmup (or cache:clear) during the build/deploy phase while the bundle directory (usually under vendor/) is still writable. Standard Pimcore deployments already do this. When assets:install runs in copy mode, run cache:warmup before it, otherwise no frontend assets are copied. If the filesystem becomes read-only before the first warmup, the bundle fails with BuildArchiveNotWritableException because there is no build to serve.

2026.1.0​

Removed Admin Classic / ExtJS Support​

  • Removed all ExtJS/Admin Classic UI related implementations.
  • PimcoreOpenIdConnectBundle no longer implements PimcoreBundleAdminClassicInterface and no longer uses BundleAdminClassicTrait. The getJsPaths() and getCssPaths() methods have been removed.
  • Removed the ContentSecurityPolicyUrlsPass compiler pass (DependencyInjection\Compiler\ContentSecurityPolicyUrlsPass) and the related build() method from PimcoreOpenIdConnectBundle.
  • Removed ExtJS controllers: Controller\AuthController, Controller\ButtonInjectionController, Controller\ConfigController.
  • Removed ExtJS-based event listeners: EventListener\LoginRedirectListener, EventListener\LostPasswordListener.
  • Removed Session\Configurator (legacy AdminSessionBagListener wrapper).
  • Removed Routing\StudioRouteLoader, studio routes are now loaded unconditionally.
  • Studio Backend and Studio UI YAML configurations are now always loaded unconditionally, instead of being gated by a bundle-presence check.
  • Removed ExtJS JavaScript assets (pimcore/startup.js, pimcore/configPanel.js, ext_extensions.js) and CSS assets (login.css, admin.css).
  • Removed legacy services_legacy.yml service definitions (Pimcore ≤ 10 compatibility).
  • Removed legacy Pimcore version checks (Version::getMajorVersion()) throughout the bundle.

New Provider Option​

  • Added the dont_overwrite_roles provider option, so roles for SSO users can be managed directly in Pimcore instead of being re-assigned from the provider's groups claim on every login. See Configuration.

Authenticator Changes​

  • OpenIdConnectAuthenticator now extends AbstractAuthenticator (Symfony) directly instead of AdminAbstractAuthenticator (Pimcore Admin bundle). Custom code extending or decorating this class must be updated accordingly.
  • Removed dependency on Pimcore\Bundle\AdminBundle\Security\Authenticator\AdminAbstractAuthenticator.

Rate Limiter Configuration​

  • Moved the rate limiter configuration for the public OIDC endpoints out of the bundle extension into a dedicated Resources/config/prepend/rate_limiter.yaml. The limiters (oidc_endpoint, oidc_script) and their values are unchanged, they were introduced in 1.6.0 (see below).

PHP / Platform Requirements​

  • Added support for PHP 8.5.
  • Removed support for PHP 8.3 and Symfony v6.

1.6.0​

Studio Backend Integration (New)​

  • Migrated legacy admin controllers to the Studio backend architecture (PR #138).
  • New Studio backend controllers added under Controller\Studio\:
    • Auth\DebugController, Auth\EndpointController, Auth\LoginController, Auth\ScriptController
    • Config\GetController, Config\UpdateController
  • New interfaces introduced (all marked @internal):
    • Hydrator\ConfigurationHydratorInterface
    • Service\Studio\Auth\EndpointServiceInterface
    • Service\Studio\Auth\LoginServiceInterface
    • Service\Studio\Auth\RenderServiceInterface
    • Service\Studio\Configuration\ServiceInterface
  • New schemas added: Schema\Configuration, Schema\EndpointParameters, Schema\ScriptParameters, Schema\SuccessResponse, Schema\UpdateConfigurationParameters.
  • New Studio frontend module added for OpenID Connect configuration and login buttons (assets/studio/).
  • Added OidcPublicAuthorizationVoter (Security\Voter\OidcPublicAuthorizationVoter) to authorize public OIDC routes within the Studio firewall.
  • Added rate limiting for the public OIDC endpoints (moved into a dedicated Resources/config/prepend/rate_limiter.yaml in 2026.1.0):
    • oidc_endpoint: fixed-window, 30 requests per 5 minutes (allows ~10 OAuth2 login attempts).
    • oidc_script: fixed-window, 50 requests per 5 minutes (for the login-page JavaScript asset).
  • Added AppConfig\OidcAppConfigProvider to supply provider names to the Studio UI app config.
  • Added Webpack\WebpackEntryPointProvider to register the Studio frontend build entry point.

This release still supported Admin Classic / ExtJS alongside the new Studio integration. 2026.1.0 (above) removed the Admin Classic support entirely.

1.2.0​

  • [General] Dropped support of Pimcore 10, bumped minimum requirement of pimcore/pimcore to ^11.2. Replaced all $request->get() with their explicit input source.
  • [Composer] Replaced the abandoned jwt related required packages with jwt-library
  • [Composer] Bumped minimum required PHP version to 8.1 and added support to 8.2 and 8.3

1.1.0​

  • [Plugins] Replaced plugins backend UI with JS event listener.
  • [Session] Replaced SessionConfigurator with OpenSessionBagListener and added related deprecation triggers.
  • [Session] Deprecated Configurator::SESSION_BAG_NAME, use OpenSessionBagListener::SESSION_BAG_NAME instead.
  • [Session] Replaced usage of deprecated Symfony\Component\HttpFoundation\Session\Attribute\NamespacedAttributeBag in favor of AttributeBag
  • If you are upgrading to Pimcore 11, install the pimcore/admin-ui-classic-bundle bundle.