Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NotificationReceiverController - Should use custom RouteScope so it works with headless sales channels as well #261

Open
AndreasA opened this issue Jun 2, 2022 · 0 comments

Comments

@AndreasA
Copy link
Contributor

AndreasA commented Jun 2, 2022

Describe the bug
With multiple sales channels the NotificationReceiverController would require a corresponding Storefront sales channel with a correct domain configuration. It will not work for headless sales channels and it might also be tricky regarding which URL to use if the sales channel has multiple or one uses the same adyen configuration for multiple sales channels.

Instead if would make more sense to either use the admin API ACL definitions with a corresponding permission
or a custom route scope defintion.
The custom route scope is probably the way to go as you can define it for the adyen prefix, and can create your own authentication which you probably need for the web hooks. It should optionally be possible to specify the sales channel ID in the URL, e.g. as query parameter or suffix.

It would probably be necessary

Versions
Shopware version: 6.4.11.1
Plugin version: 3.4.1

@AndreasA AndreasA changed the title Adyen\Shopware\Storefront\Controller\NotificationReceiverController - Should use custom RouteScope so it does not require a corresponding sales channel domain NotificationReceiverController - Should use custom RouteScope so it works with headless sales channels as well Jun 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant