[BP-2062] Afterpay customer IP doesn't follow IP header from config about magento2 HOT 6 CLOSED

@stefanfr,

Thanks for reporting this issue. We're going to look into this as soon as possible.

from magento2.

@stefanfr ,

We created a ticket for this issue with the following reference: BP-2062
It is currently on our backlog. When we have more information about the sprint schedule or status change etc, we'll let you know.

from magento2.

Hi @Buckaroo-Rens @Buckaroo-Rene,

After receiving an email from Chitra I noticed my earlier post isn't clear. The issue is not that we cannot change the config to follow our specific ip headers but that the buckaroo method doesn't use this flow.

If I check the flow for Ideal I see this configuration being used in file Gateway/Http/TransactionBuilder/AbstractTransactionBuilder.php on line 532 the function getIp is called, here this config is used $ipHeaders = $this->configProviderAccount->getIpHeader($store);

However when I check the Afterpay, now Riverty, flow I see that the customerData is build with only the remote address:

$customerData = [
        [
            '_'    => $this->getRemoteAddress(),
            'Name' => 'CustomerIPAddress',
        ],
        [
            '_'    => $accept,
            'Name' => 'Accept',
        ]
    ];

$this->getRemoteAddress() should include the $alternativeHeaders parameter to correctly set the customer Ip

from magento2.

Thanks for your additional info @stefanfr, we will look into this asap.

from magento2.

@stefanfr We are currently preparing a new release (1.44.0). A fix for your issue is included in this new release.
We'll let you know when the release is done (probably somewhere next week).

from magento2.

Hi @stefanfr ,

We've just released version 1.44.0 of the Buckaroo Plugin.
A fix for this issue is included BP-2062

from magento2.