Skip to main content
Question

Cisco ISE - JAMF integration

  • February 10, 2020
  • 3 replies
  • 11 views
G
Forum|alt.badge.img+5

We are implementing Cisco ISE in our network, and we would like to use Jamf as a means to identify and recognize manages Apple devices.
ISE query's Jamf’s inventory, and gets the device’s MAC address in response. If this MAC address exists in Jamf, ISE will continue to query all other info about this device.

The issue we encounter is that only the “en0" MAC address is sent to ISE.
If more then one network hardware connection exists, (e.g. usb network adapters, wifi adapters) different for en0, Jamf response is that the device is not part of the repository, and ISE doesn’t recognize it.
Is there a way to use all the MAC addresses as reference objects for Jamf into ISE?

    3 replies

    D
    Forum|alt.badge.img+18
    • dgreening
    • Honored Contributor
    • 645 replies
    • February 10, 2020

    I believe that ISE 4.6+ supports using the UDID of the machine instead of the MAC address. This is obviously preferable if you can do it!

    G
    Forum|alt.badge.img+5
    • gurduv
    • Author
    • Contributor
    • 15 replies
    • May 27, 2020

    Our ISE is version 2.6.0.156
    What ISE implementation did you mean?

    M
    Forum|alt.badge.img+10
    • mrheathjones
    • Contributor
    • 29 replies
    • May 27, 2020

    @gurduv We are running an older version of ISE (2.6.x I believe), and we had the same issue. To get around it I wrote a policy that does the following:

    1. Gets the ethernet adapter's MAC address and adapter name
    2. updates the Jamf record fields (Primary MAC Address and Primary Network Adapter Type) via API
    3. Gets the ISE NAS IP address
    4. forces an ISE re-auth via API

    We are currently only having ISE performing Posture checks on wired connections with plans on expanding to wireless. My workaround is definitely hacky, but it's been working. Only problem is the when the device checks-in that Primary MAC Address is then written over with the en0 info. My policy runs on network state change and check-in, so that limits the the "posture check fail" in reports ISE. Hope this helps.


    Terms & ConditionsCookie settingsAccessibility statement