cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
cybertunnel
Frequent Visitor

Jamf Pro's Webhook Gets 401 Response

Good Afternoon,

 

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.

6 REPLIES 6
v-bacao-msft
Community Support
Community Support

 

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?

 

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

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

did you ever get this working, im trying to figure out the connection to jamf as well.

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.

geoffreykobrien
New Member

thanks for that, do you have an example flow that I could reference for doing that?

cybertunnel
Frequent Visitor

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...

You would switch it to `https://prod-01.westus.logic.azure.com:443/workflows/c1eb430f20b44e4e9d16b04079b189f3/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.

Helpful resources

Announcements
MPA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

MBAS on Demand

Microsoft Business Applications Summit sessions

On-demand access to all the great content presented by the product teams and community members! #MSBizAppsSummit #CommunityRocks

MBAS Attendee Badge

Claim Your Badge & Digital Swag!

Check out how to claim yours today!

secondImage

Are Your Ready?

Test your skills now with the Cloud Skill Challenge.

Top Solution Authors
Users online (48,163)