[BUG] Service Configurations for Client Encryption Java MDES Token Connect - missing Push Multiple Accounts configuration

[Mikolaj-Walkowiak]

Bug Report Checklist

• Have you provided a code sample to reproduce the issue?
• Have you tested with the latest release to confirm the issue still exists?
• Have you searched for related issues/PRs?
• What's the actual output vs expected output?

Description
In the "Service Configurations for Client Encryption Java", the section "MDES Token Connect" misses the Encryption Path for the new Push Multiple Accounts payload. Using the default config results in an INVALID_JSON error.

To Reproduce
Use the provided FieldLevelEncryptionConfigBuilder for the MDES Token Connect.

Expected behavior
The payload is correctly encrypted.

Suggest a fix/enhancement
Add
.withEncryptionPath("$.pushFundingAccounts.encryptedPayload.encryptedData", "$.pushFundingAccounts.encryptedPayload")
to the provided config, optionally mark
.withEncryptionPath("$.pushFundingAccount.encryptedPayload.encryptedData", "$.pushFundingAccount.encryptedPayload")
as obsolete (or remove it altogether).

[ShimonaR-MC]

Hi Mikolaj-Walkowiak, thanks for bringing this up.

The example configuration documented in the README is applicable to Push Account: POST /connect/{maj}/pushAccount.
.withEncryptionPath("$.pushFundingAccount.encryptedPayload.encryptedData", "$.pushFundingAccount.encryptedPayload")
This endpoint is deprecated, but is functional at the moment and works correctly when used with the given configuration.
We acknowledge that this wasn't clear in the README (Service Configurations for Client Encryption Java section), and we have updated it to reflect the same.

The endpoint Push Multiple Accounts: POST /connect/{maj}/pushMultipleAccounts expects the following configuration like you have mentioned.
.withEncryptionPath("$.pushFundingAccounts.encryptedPayload.encryptedData", "$.pushFundingAccounts.encryptedPayload")

Thank you.

[ShimonaR-MC]

Closing with documentation update.