Auth.net module sending OPTIONS request

[nbennett25]

Using Magento 2.3.3 and the new Auth.net Payment method, configuration with a sandbox account throws an error in the OPTIONS API call. I've been in touch with Auth.net's support, and they have made it clear that the API does not even support OPTIONS requests, so it seems like this is likely a Magento issue.

Preconditions (*)

1. Magento 2.3.3
2. Auth.net sandbox account configured
3. Credentials from Auth.net account added to admin configuration
4. Payment method enabled

Steps to reproduce (*)

1. Add product to cart
2. Go to Checkout
3. Fill out Shipping Address
4. Click 'Next'
5. Select Credit Card (Authorize.net) from Payment Method
6. Enter test credit card field values
7. Click 'Place Order'

Expected result (*)

1. Order goes through, user is sent to the success page

Actual result (*)

1. OPTIONS request sent to https://apitest.authorize.net/xml/v1/request.api
2. Error received: "code":"E00001","text":"Error reading JToken from JsonReader. Path '', line 0, position 0."
3. POST request sent to https://apitest.authorize.net/xml/v1/request.api
4. Error received: "code":"E00007","text":"User authentication failed due to invalid authentication values."
5. Error displayed to user: User authentication failed due to invalid authentication values
6. User is not sent to success page

[m2-assistant[bot]]

Hi @nbennett25. Thank you for your report. To help us process this issue please make sure that you provided the following information:

• [ ] Summary of the issue
• [ ] Information on your environment
• [ ] Steps to reproduce
• [ ] Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@nbennett25 do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• [ ] yes
• [ ] no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[nbennett25]

@magento give me 2.3.3 instance

[magento-engcom-team]

Hi @nbennett25. Thank you for your request. I'm working on Magento 2.3.3 instance for you

[magento-engcom-team]

Hi @nbennett25, here is your Magento instance. Admin access: https://i-26376-2-3-3.instances.magento-community.engineering/admin Login: admin Password: 123123q Instance will be terminated in up to 3 hours.

[nbennett25]

@magento confirmed same behavior on 2.3.3 instance.

[m2-assistant[bot]]

Hi @engcom-Charlie. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• [ ] 5. Add label Issue: Confirmed once verification is complete.

• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

:white_check_mark: Confirmed by @engcom-Charlie Thank you for verifying the issue. Based on the provided information internal tickets MC-30447 were created

Issue Available: @engcom-Charlie, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[nbennett25]

Any updates here?

[nbennett25]

@magento give me 2.3.2 instance

[magento-engcom-team]

Hi @nbennett25. Thank you for your request. I'm working on Magento 2.3.2 instance for you

[magento-engcom-team]

Hi @nbennett25, here is your Magento instance. Admin access: https://i-26376-2-3-2.instances.magento-community.engineering/admin_953e Login: cd987667 Password: 2b49de3107db Instance will be terminated in up to 3 hours.

[nbennett25]

Also confirmed on 2.3.2

Noting that I received a confirmation email from the Auth.net sandbox that the transaction was approved despite seeing the same behavior and error on the front end of the 2.3.2 instance.

[nbennett25]

@magento @engcom-Charlie @magento-engcom-team - if this is not going to be worked on in the immediate future, can we at least get a patch file?

There are now reports of the same issue affecting live/production Auth.net integrations

[Beowulf891]

@magento-engcom-team @magento I must agree with @nbennett25. This issue is affecting live accounts and needs a resolution ASAP!

[m2-assistant[bot]]

Hi @dharmendra-wagento. Thank you for working on this issue. Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• [ ] 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 2. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• [ ] 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[dharmendra-wagento]

mm20in

[nbennett25]

It looks like Magento 2.3.4 has officially deprecated all core Auth.net payment methods, and requests that users install the Auth.net provided module (composer require authorizenet/magento-module-authorizenet), however it looks like that module may have issues as well.

[sdzhepa]

Hello @nbennett25

Thank you for your report and collaboration!

Unfortunately, we are closing this Issue report because we are not able to process contribution to the 2.3.x release line through this public repository. See details Code Contributions: Accepted pull requests and ported code

And starting from 2.4.0 release, code related to this payment was removed/deprecated from Magento code-base: Magento Commerce 2.4.0 Release Notes

With this release, the Authorize.Net, Braintree, eWay, CyberSource, and Worldpay payment method integrations have been removed from core code. Merchants should migrate to the official extensions that are available on the Magento Marketplace.

Deprecation of Magento core payment integrations

All questions, issue reports and fix for them should be addressed to the corresponding extension owners(support) on the Magento Market place page