I am confused how this should work:
What i have read from documentation is that the device never hits the /EWS site on exchange directly to handle the subscription, this is done via the ENS v2 Server.
With KCD in use and after enabling the SEG v2 to also handle EWS requests i guess via Appconfig for Boxer the EWSUrl should point to the SEG and not to exchange, correct?
But this only means that the ENS server sends the request to SEG EWS URL -> How can the ENS v2 do this without the private key of the user certificate?
Did you get an answer to this? I'm trying to configure this currently for our environment (on-prem). The support team I was working with recommended ENS auth via your Exchange directly, instead of the SEG. Although we still could not get it working this way, they recommended using professional services for deployment.
Hi,
Have you get this working?
Im trying to set up ENSv2 with KCD thru SEG, but cant get this work. I can see in the ENS logs that the push notification subscription are successfully. But then nothing more will happen....
Does anyone have an idea of what the error might be?