Closed daceej closed 3 years ago
Hi @daceej. 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.4-develop instance
- upcoming 2.4.x release
For more details, please, review the Magento Contributor Assistant documentation.
Please, add a comment to assign the issue: @magento I am working on this
Join Magento Community Engineering Slack and ask your questions in #github channel.
:warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
:clock10: You can find the schedule on the Magento Community Calendar page.
:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.
:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel
:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel
To clarify, this is likely outside of any scope as I found this issue due to a customization. However, it took far too long to figure out what was happening, so I'm flagging it as a potential enhancement in the future.
Maybe this will be useful to someone in the future. :)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!
Preconditions (*)
Steps to reproduce (*)
vault_payment_token
Expected result (*)
Actual result (*)
PaymentTokenManagement::getByGatewayToken($token, $paymentMethodCode, $customerId)
.vault_payment_token
table has a unique index on the (customer_id, token, and payment method type) as well as a unique index on the public hash.I suspect adding the public hash to the multi key unique index on the
vault_payment_token
table would resolve this, but there may be other implications there that I'm not aware of.Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.