You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have the URL registered in the Email Developer Dashboard, and I am testing sending self-to-self.
The application that should be getting hit is an ASP .NET Core app using Microsoft Identity / Azure AD, so I wasn't sure whether I needed to be setting the Authorization header to a blank string there or not... I figured that my application actually uses the Authorization header for Auth to my own site/app, so it would be better to receive any identity info from Outlook via the alternative Action-Authorization header instead. I've got code ready-to-go for decoding that token/claims object once I receive it, and verifying that the actor clicking the button is who I expect it to be - but at the moment, the endpoint is just never hit at all.
This endpoint allows anonymous access and is configured for CORS, I can send a dummy request to this endpoint and hit my breakpoints just fine - so I know it's working in terms of my Web API...
My problem is that Outlook and Outlook for Web don't seem to trigger it. Am I doing something wrong? When the action button is pressed I can see this payload and response in developer tools:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a card with an approval action button like this:
I have the URL registered in the Email Developer Dashboard, and I am testing sending self-to-self.
The application that should be getting hit is an ASP .NET Core app using Microsoft Identity / Azure AD, so I wasn't sure whether I needed to be setting the
Authorization
header to a blank string there or not... I figured that my application actually uses theAuthorization
header for Auth to my own site/app, so it would be better to receive any identity info from Outlook via the alternativeAction-Authorization
header instead. I've got code ready-to-go for decoding that token/claims object once I receive it, and verifying that the actor clicking the button is who I expect it to be - but at the moment, the endpoint is just never hit at all.This endpoint allows anonymous access and is configured for CORS, I can send a dummy request to this endpoint and hit my breakpoints just fine - so I know it's working in terms of my Web API...
My problem is that Outlook and Outlook for Web don't seem to trigger it. Am I doing something wrong? When the action button is pressed I can see this payload and response in developer tools:
Payload:
Response
In the Outlook Actionable Message Debugger I can see this additional information under diagnostics:
Any help most appreciated!
Tom
Beta Was this translation helpful? Give feedback.
All reactions