Troubleshooting Tip: Failed to Read JAMF Info

[khoffman]

Description	This article describes how to determine why FortiNAC is unable to communicate with the JAMF MDM Service connector when 'right-clicking' on the JAMF service connector within FortiNAC and selecting 'Test Connection' or 'Poll Now' results in the following Error:  Failure: Failed to read Jamf Info
Scope	FortiNAC v9.2, FortiNAC v9.4 and FortiNAC-F v7.2+ .
Solution	Validate the following:  Verify the password does not contain '@; character. This can cause authentication failure.  Verify that Basic Authentication is the Classic API is enabled on the JAMF server. Verify the Request URL entered in the FortiNAC MDM Service connector does not contain a trailing '/'. Example:  Invalid: https://example.jamfcloud.com/ Valid: https://example.jamfcloud.com If steps 1-3 do not resolve the issue:  Log in to the CLI of FortiNAC and enable the following to debug:  CentOS (log in as root): nacdebug -name JamfServer true nacdebug -name MdmManager true FortiNAC-OS (log in as admin): execute enter-shell nacdebug -name JamfServer true nacdebug -name MdmManager true Generate the error from the Admin UI by selecting 'poll now' or 'Test Connection'.  Collect a grab-log-snapshot. Related article: How to get a debug log report from FortiNAC Disable debug: CentOS (log in as root) nacdebug -name JamfServer false nacdebug -name MdmManager false FortiNAC-OS (log in as admin) execute enter-shell nacdebug -name JamfServer false nacdebug -name MdmManager false Open a support ticket with the following information:  Description of the behavior.  Screen captures of JAMF MDM service connector.  log-snapshot.