ÃÛ¶¹ÊÓƵ Commerce 2.4.7-p4 HIPAA 1.2.0 compatibility package Hotfix
This article provides a hotfix to add compatibility for the new HIPAA package 1.2.0 with ÃÛ¶¹ÊÓƵ Commerce on Cloud infrastructure 2.4.7-p4.
The issue will be fixed in the version 2.4.7-p5 release.
Affected versions and products
ÃÛ¶¹ÊÓƵ Commerce on Cloud infrastructure 2.4.7-p4 and earlier
Prerequisites
- ÃÛ¶¹ÊÓƵ has provisioned your ÃÛ¶¹ÊÓƵ Commerce account to access the HIPAA Ready extension. See HIPAA readiness on ÃÛ¶¹ÊÓƵ Commerce for more details in our ÃÛ¶¹ÊÓƵ Commerce: Getting Started Guide.
- Access to to install the extension. For key generation and obtaining the necessary rights, see Get your authentication keys in our ÃÛ¶¹ÊÓƵ Commerce: Installation Guide.
Issue
The HIPAA package 1.1.0 isn’t compatible with ÃÛ¶¹ÊÓƵ Commerce 2.4.7x release line.
Solution
Through this hotfix, merchants who are running ÃÛ¶¹ÊÓƵ Commerce on Cloud infrastructure 2.4.7-p4 will able to use the HIPAA package 1.2.0.
If you aren’t on ÃÛ¶¹ÊÓƵ Commerce 2.4.7-p4, you must first upgrade to ÃÛ¶¹ÊÓƵ Commerce 2.4.7-p4 in order to use this patch.
To fix the issue for ÃÛ¶¹ÊÓƵ Commerce on Cloud infrastructure 2.4.7-p4, you should apply the patch:
²¹³¦-13382â€Ëð²¹³Ù³¦³ó-´Ú´Ç°ù-³ó¾±±è²¹²¹-2-4-7-±è4-³¦´Ç³¾±è´Ç²õ±ð°ù-±è²¹³Ù³¦³ó.³ú¾±±è
How to apply the patch
Unzip the file and see How to apply a composer patch provided by ÃÛ¶¹ÊÓƵ in our support knowledge base for instructions.
For ÃÛ¶¹ÊÓƵ Commerce on Cloud merchants only - How to tell whether the patch has been applied
Considering that it isn’t possible to easily check if the issue was patched, you might want to check whether the patch has been successfully applied.
VULN-27015-2.4.7_COMPOSER.patch as an Example:-
Run the command:
-
You should see output similar to this, where the Example used here, VULN-27015, returns the  Applied  s³Ù²¹³Ù³Ü²õ:
code language-bash ║ Id │ Title │ Category │ Origin │ Status │ Details ║ ║ N/A │ ../m2-hotfixes/VULN-27015-2.4.7_COMPOSER_patch.patch │ Other │ Local │ Applied │ Patch type: Custom