[BUG] #5149
Description
Reporting an Issue or Missing Feature
Issue
Expected behavior
Event Receivers are not only added, but are also firing
Actual behavior
When adding Remote Event Receivers via Add-PnpEventReceiver-Command, the Function is executed and the Receivers are obviously registered to the List. However, they do not fire. Formerly it was meant, that this is an issue due to MS uses internal stuff and more details, I do not want to go into now. It had to do with the fact, that the Registration was done while being authorized via token. It did work with the old "useWeblogin" method, because this was cookie based authentication.
However, "now" MS released an migration guide to move from ACS-based RERs to ones using EntraId app registrations (https://learn.microsoft.com/en-us/sharepoint/dev/sp-add-ins-modernize/use-remote-event-receivers-without-azure-acs-dependency). I am able to register a EventReceiver, tough it is not fired. Maybe I missed something, maybe MS did not check, when writing this doc, if they are actually firing when registered it that way?
If there is now only token-based authentication in PnP.Powershell, either that commandlet should be able to produce actually firing RER´s, or it should be removed completely.
Steps to reproduce behavior
Register an Event receiver using the PNP-Commandlet "Add-PnPEventReceiver" and check if it actually is also triggered (and not only registered)
What is the version of the Cmdlet module you are running?
3.1
Which operating system/environment are you running PnP PowerShell on?
- [ x] Windows
- [ x] Linux
- MacOS
- Azure Cloud Shell
- Azure Functions
- Other : please specify
How I register the RER:
Looking at an eventsink for received request triggered by the EventReceivers (LeoTestOld is an RER, registerd with the old SharepointPnpPowershell modules, which goes to the /old path, the one registered with the current version and entraId is supposed to end up in the "/sub" path, but it does not appear )
Permissions of my AppRegistration:
