tuxudo / jamf Goto Github PK

tuxudo/jamf

@tuxudo Per Slack conversation, please update the listing's search logic.

I successfully upgraded to MunkiReport Version 5.6.4.4224 some time ago and I’m just now looking at https://FQDN/show/report/jamf/jamf

Drilling down on some of the widgets works as expected …

• Last Check-in: https://FQDN/show/listing/jamf/jamf
• XProtect Definitions Version: https://FQDN/show/listing/jamf/jamf/#2135

… while others result in “Page not found” errors:

• Automatic Login Disabled: https://FQDN/show/listing/jamf/jamfdisable_automatic_login%20=%201
• Purchased or Leased: https://FQDN/show/listing/jamf/jamfpurchased%20=%201
• User Approved Enrollment: https://FQDN/show/listing/jamf/jamfuser_approved_enrollment%20=%200

Patch related endpoints have broken JSON. Something to do with how XML is turned into JSON on the server. Instead of an array it becomes a hash/dict with one key holding the last value only, all others are missing.

XML response is complete. Is there a way to capture at the very least the patch endpoints as XML and convert them to JSON instead of letting the Classic API do it?

Credit to glenfarclas17 https://macadmins.slack.com/archives/C0EP2SNJX/p1553188123075100?thread_ts=1553175359.046300&cid=C0EP2SNJX

First, thank you John for your excellent module; first-class.

Links to Jamf Pro reference the MunkiReport FQDN instead of "JAMF_SERVER" FQDN as specified in .env, resulting in:
Error: Page not found

Steps to reproduce:

1. Login to MunkiReport
2. Navigate to Listings > Jamf
3. Click any displayed record
4. Click the "View in Jamf" button
5. "Error: Page not found" is displayed
6. Observe the URL is: MunkiReportFQDN/computers.html?id=1&o=r&v=inventory