We use a product called Jamf Pro here where I work. We have an issue where when using the HTTP Request trigger, we get a 401 response when the application does the POST to the MS Flow. However, if I have the Jamf Webhook do a POST to a server and that server then spits the POST data to MS Flow, it works as expected.
Anyone know why I could be getting a 401 on a HTTP Request triggered Flow? Any possible solutions?
P.S: I don't even see a run occur, it has no evidence of getting the request.
Hi @cybertunnel ,
If the error code is displayed as 401, it means that the current user may not have permission to access specific resources and needs to be authenticated.
Could you share the detailed configuration of Flow?
Thanks for the response.
So the flow is pretty simple, the flow is triggered by a HTTP Request and just sends a response for now of a 200. I can do a curl, post, etc on any other means. However when the application we use attempts to do a HTTP request it gets a 401
Yes, turns out Jamf does URI encoding, but Power Automate already did URI encoding. So you basically have to decode the URI encoded URL, and put it into Jamf. Which is where it encodes it properly and then it begins working again.
Sure, so the example would be:
Power Automate's HTTP Request gives you https://prod-01.westus.logic.azure.com:443/workflows/c1eb430f20b34e4e9d16b14079b189f3/triggers/manua...
Basically replacing %2F with / since Jamf will do URI encoding when it performs the request. I was only able to figure this out then I was looking at the DEBUG logs in Jamf Pro.
Check out the new Process Advisor community forum board!
Check out new user group experience and if you are a leader please create your group
On-demand access to all the great content presented by the product teams and community members! #MSBizAppsSummit #CommunityRocks
Check out how to claim yours today!