Unanswered

Jamf Pro's Webhook Gets 401 Response

(0) Share

Report

Posted on by cybertunnel

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.

Categories:

Using flows

I have the same question (0)

All responses (6)

Answers (0)

Sort by

v-bacao-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

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,

Was this reply helpful? Yes No
cybertunnel 6 on at

Like (0)

Report
Copy link

Link copied!

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

Was this reply helpful? Yes No
geoffreykobrien 4 on at

Like (0)

Report
Copy link

Link copied!

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

Was this reply helpful? Yes No
cybertunnel 6 on at

Like (0)

Report
Copy link

Link copied!

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.

Was this reply helpful? Yes No
geoffreykobrien 4 on at

Like (0)

Report
Copy link

Link copied!

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

Was this reply helpful? Yes No
cybertunnel 6 on at

Like (0)

Report
Copy link

Link copied!

Sure, so the example would be:
Power Automate's HTTP Request gives you https://prod-01.westus.logic.azure.com:443/workflows/c1eb430f20b34e4e9d16b14079b189f3/triggers/manual/paths/invoke?api-version=2016-06-01&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=PAyfkUq-N6y9o9BS1m_Ak6tRFxrffGXWQz039U
You would switch it to `https://prod-01.westus.logic.azure.com:443/workflows/c1eb430f20b44e4e9d16b04079b189f3/triggers/manual/paths/invoke?api-version=2016-06-01&sp=/triggers/manual/run&sv=1.0&sig=PAyfkUq-N6y9o9BS1m_AuyMv3k6tRFxrffGXWQz039U

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.

Was this reply helpful? Yes No