I am trying to get some additional attributes from my Jamf Pro instance and running into issues, so have been parsing through various docs until I finally found the v.5.0 release notes (the v5 extension application itself links to only the v4.2 documentation). So as I am reading through the v5 release notes, there are additional links as to the disparage between Jamf Classic API and Jamf Pro API field names. So, is it safe to assume, based on Jamf's document
Deprecation of Classic API Computer Inventory Endpoints
That the attributes later professed in both the ClearPass Jamf extension document for v4.2 and v5 Appendix A, are in fact still only for Jamf Classic API and the need to replace said attribute mappings with the linked article above to the Jamf Pro API mapping is required.
Soo just to clarify, since I have been trying to add additional attribute mappings via the extension config and not having any luck...I am now assuming what was, for example, "location.username" is now in fact, "userAndLocation.username" (again, based on the Jamf link above) if I have HPE recommended "enableV2Api" set to true, correct? And will it auto-create those those dictionary attributes too?
-------------------------------------------