Adobe Commerce 2.4.3 ends on November 28. Ensure your store is up-to-date!
Adobe, one of the powerful eCommerce platforms, to maintain keeps updating its version to stay contemporized with technology, execution, and security.
Rootways's specialist research team prepared guidelines for upgrading Magento 2, which can help update your store. Let's track this guide step by step.
On November 28, 2022, support for Adobe Commerce versions 2.4.0 through 2.4.3 will stop, coinciding with the end of PHP 7.4 support. Digital stores still using 2.4.x after this date will look after their security and PCI compliance. Before these dates, Adobe advises upgrading to Adobe Commerce 2.4.4 to benefit from new features and ongoing support.
Additional Assistance
Adobe will provide an opportunity to provide additional support to your license for up to one year beyond the EOS date for any individual Commerce version built on PHP 7.4 to users who require more time to move to 2.4.4. To learn more details, kindly get in touch with your account manager or customer success manager.
About Adobe commerce 2.4.3
Although the source code for these features is included in the Magento core code's quarterly releases, several projects—like B2B, Page Builder, and Progressive Web Applications (PWA) Studio—are distributed separately. In addition, the separate, project-specific release information accessible in the documentation for each project contains details on the bug fixes for these projects.
The performance and security of the latest version of Adobe Commerce have undergone numerous changes. The reCAPTCHA coverage has been expanded in Adobe Commerce 2.4.3, and a built-in rate restriction has also been included. To be compatible with PHP 8 and newer, third-party libraries and core composer requirements have also been updated.
Why should you upgrade to the latest version of Adobe Commerce?
- Email variable usage was discontinued in the older version in Favour of a more powerful variable syntax as a security risk reduction measure. This version removes the legacy behavior as part of that security risk minimization.
- As a result, when upgrading to Adobe Commerce 2.4.4 or Magento Open Source 2.4.4, email or newsletter templates that were compatible with earlier releases of Adobe Commerce might not function properly. Admin overrides, themes, child themes, and templates from unique modules or third-party extensions are among the affected templates. Even after using the Upgrade compatibility tool to correct deprecated usages, your deployment may still be impacted. For details on possible implications and instructions on migrating impacted templates, see Migrating custom email templates.
- Integration tokens can no longer be used to authenticate API Bearer tokens. Previously, a separate key for token-based authentication could be created using an integration token. A never-expiring access token has security issues; hence this feature has been deactivated by default. Admin or the command line can be used to enable the previous behavior. Check out Token-based authentication.
- No longer are session IDs kept in the database.
- The database now stores OAuth access tokens and password reset tokens in encrypted form.
- Validation has been enhanced to stop uploading file extensions that are not alpha-numeric.
- Coupon codes now support reCAPTCHA.
- When Adobe Commerce is in production mode, Swagger is deactivated by default.
- The Adobe Commerce storefront now has HTTPS enabled by default. In addition, all built-in cookies are currently configured as secure, and the Use Secure URLs on Storefront and Use Secure URLs in Admin settings are also activated by default.
- All Adobe Commerce installations now demand the dependency confusion plugin. This plugin was previously solely necessary for Composer-based setups. Trusted versions are now permitted. The limitations imposed by this plugin, which forbid particular combinations of Composer installations, can be circumvented by merchants. The restrictions can be disregarded for trustworthy versions, and Adobe Commerce now warns users before installing.
- Developers may set the maximum size of arrays that Adobe Commerce RESTful endpoints can accept. Look into API security.
Summary
If you need information or have queries that are not covered in these guidelines, Contact us for further details.
Rootways offer Upgrade to the latest Magento 2 version,
We want to hear your feedback or any issues to assist us in improving our services.
Magento Version Upgrade