Closed neha023 closed 5 years ago
Hi @neha023. Thank you for your report. To help us process this issue please make sure that you provided the following information:
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.3-develop instance
- upcoming 2.3.x release
For more details, please, review the Magento Contributor Assistant documentation.
@neha023 do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?
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.3-develop
branchDetails
- Add the comment @magento give me 2.3-develop instance
to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.3-develop
branch, please, add the label Reproduced on 2.3.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. Verify that the issue is reproducible on 2.2-develop
branch. Details
- Add the comment @magento give me 2.2-develop instance
to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.2-develop
branch, please add the label Reproduced on 2.2.x
[ ] 6. Add label Issue: Confirmed
once verification is complete.
[ ] 7. Make sure that automatic system confirms that report has been added to the backlog.
Hello @neha023 ! Can you confirm that you can reproduce this issue on Vanilla Magento ?
Hi,
I have found that people are able to checkout via authorized.net but they have found the issue that orders are created with cancel status in magento 2.3.1 and this issue will fixed by you guys in Magento 2.3.2 release. So my issue is faced by some of the people not by everyone. As we have found issue after upgrade from M2.2.5 to M2.3.1. Same issue link I found on magento stack: https://magento.stackexchange.com/questions/277948/authorize-net-issue-with-magento-2-3-1-invalid-gateway-credentials
Thanks.
On Thu, Jun 20, 2019 at 7:05 PM engcom-Charlie notifications@github.com wrote:
Hello @neha023 https://github.com/neha023 ! Can you confirm that you can reproduce this issue on Vanilla Magento ?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/magento/magento2/issues/23256?email_source=notifications&email_token=AFOSYYCEQES5SEYL3OZNNTTP3OBQZA5CNFSM4HYFKAYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYFNUHY#issuecomment-504027679, or mute the thread https://github.com/notifications/unsubscribe-auth/AFOSYYBS7D3I63TDBS2H4TTP3OBQZANCNFSM4HYFKAYA .
-- Thanks & Regards (please excuse any typos),
SINGAPORE OFFICE SunArc Technologies Pte. Ltd. 171 Tras Street, #04-171A, Union Building, Singapore 079025
INDIA DEVELOPMENT CENTER SunArc Technologies Pvt Ltd. Novel Tech Park, Kudlu Gate, Bangalore
SunArc Technologies Pvt Ltd. 29-30 Panchshati Circle Bikaner RJ 334003 India T: +91.151.220.0810, 2202140 W: www.sunarctechnologies.com
https://www.facebook.com/sunarctechnologies https://plus.google.com/118054332794463441394 https://www.linkedin.com/company/sunarc-technologies https://twitter.com/SunArc_tech https://www.youtube.com/channel/UCiMpzCTSjdhyfaa3PGiwExg
Warning: Privileged/Confidential information may be contained in this communication (which includes any attachment). If you are not an intended recipient, you must not use, copy, disclose, distribute or retain this communication or any part of it. Please delete all copies of this communication from your computer system and notify the sender immediately by reply mail.
The sender does not accept any responsibility for any loss, disruption or damage to your data or computer system which may occur whilst using data contained in, or transmitted with, this email. Any views or opinions represented in this email are solely those of the author and may not necessarily represent those of SunArc Technologies Pvt Ltd.
@neha023 I ran into the same "User authentication failed due to invalid authentication values." issue after updating to 2.3.2. If you update to 2.3.2 and are still having that same issue, try doing what I mentioned in my latest comment in this thread https://github.com/magento/magento2/issues/22373
Preconditions (*)
Steps to reproduce (*)
Got and error message on screen "Invalid Gateway Credentials."
In console :
Expected result (*)
Actual result (*)
I have verified credentials many times and re-enter again and again but the issue remains same. The credentials are working fine on M2.2.5 site but having issue with M2.3.1. Thanks.