fix: remove sensitive information from the client side

[vinhtrinh]

Summary

Describe the changes proposed in this pull request:

• Sensitive Adyen information is currently exposed to the client side through application configurations.
• To address this security issue, we need to relocate the Adyen configurations to a more secure location, such as config/{siteId}/adyen.js.
• This PR includes a cloned script from a new feature request in the PWA main repository.
  • Once the PR in @salesforce/pwa-kit is approved and merged, we can remove this temporary module.
  • If the PR is not approved, we can retain the custom getConfig module as a permanent solution.

Types of Changes

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Documentation update
• Breaking change (could cause existing functionality to not work as expected)
• Other changes (non-breaking changes that does not fit any of the above)

Examples of usage:

// file: config/RefArch/adyen.js
module.exports = {
    apiKey: process.env.ADYEN_API_KEY,
    clientKey: process.env.ADYEN_CLIENT_KEY,
    environment: process.env.ADYEN_ENVIRONMENT,
    merchantAccount: process.env.ADYEN_MERCHANT_ACCOUNT,
    systemIntegratorName: process.env.SYSTEM_INTEGRATOR_NAME,
    webhookUser: process.env.ADYEN_WEBHOOK_USER,
    webhookPassword: process.env.ADYEN_WEBHOOK_PASSWORD,
    webhookHmacKey: process.env.ADYEN_HMAC_KEY
}

// Gets Adyen configurations from default `RefArch` site
import {getSiteConfig} from '@salesforce/pwa-kit-runtime/utils/ssr-config'

const adyenConfig = getSiteConfig('adyen')

General

• Changes are covered by test cases
• There are no changes to UI

Fixed Issue: #97
Resolved By: SalesforceCommerceCloud/pwa-kit#1639

[sonarcloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[amihajlovski]

Hello @vinhtrinh

This PR will add extra dependencies and we don't want to do that.
We are working on another solution that will keep the environment variables on the backend only.

Kind Regards
Aleksandar
Adyen